Travel compliance detection using body-worn offender monitoring electronic devices

ABSTRACT

A body-worn tracking device (BWTD) includes a global navigation satellite system (GNSS) device, a cellular communication unit, at least one processor, and at least one memory device. The at least one memory device includes instructions that, when executed by the at least one processor, cause the at least one processor to determine whether the BWTD is located on board an aircraft. Execution of the instructions further causes the at least one processor to, responsive to determining that the BWTD is located on board the aircraft: disable the GNSS device and the cellular communication unit; and temporarily refrain from generating an alert that indicates a current location of the BWTD cannot be determined.

TECHNICAL FIELD

This disclosure relates to information systems for tracking geospatiallocation information related to monitored persons or objects.

BACKGROUND

Released criminal offenders on community supervision, either probationor parole, may be monitored with body-worn tracking devices (BWTDs) by acriminal justice supervising agency, such as a department of correctionsor local law enforcement. The monitoring is based on a sentence, andoften includes restricted regions and permissible regions with aschedule for the day of the week and a range of times associated withthose areas when the released criminal offender is required to be orrequired not to be in those areas. A released criminal offender'sgeospatial location at a given date and time is monitored and recordedby tracking devices worn or carried by the released criminal offender.This geospatial information, including date and time information, can beused to determine a released criminal offender's compliance with theirsentence. Activities of released criminal offenders can be reported tothe criminal justice supervising agency or to a probation or paroleofficer by fax, page, text message or email generated by a monitoringcenter unique to the criminal justice supervising agency.

SUMMARY

Techniques of this disclosure are directed to detecting compliance withpermitted travel plans using a body-worn tracking devices (BWTD) worn bya monitored person. In some examples, a computing device (e.g., aprocessor of a BWTD, a local computer, a server of a monitoring system,etc.) determines whether the BWTD is on board a permitted vehicle (e.g.,in an automobile, train, aircraft, marine craft, etc.) when the vehicleprevents the BWTD from determining its GPS coordinates. For example, amonitored person may be permitted to travel to a particular destinationvia a particular flight. In some instances, the computing device maydetermine whether the BWTD is on board an aircraft. In some instances,the computing device may determine whether the BWTD is on board thecorrect aircraft (e.g., an aircraft flying the particular flight) to thepermitted destination. In some example implementations, the computingdevice may determine whether the BWTD is on board an aircraft based on awireless connection between the BWTD and one or more non-cellularwireless communication systems (e.g., via a connection between the BWTDand an WiFi® system on board the aircraft).

Rather than outputting alerts (e.g., notifying law enforcementpersonnel) that a monitored person is potentially in violation of his orher parole when the GPS coordinates of the BWTD are unavailable, in someexamples, the computing device may temporarily refrain from outputtingalerts in response to determining that the BWTD is on board an aircraft.Refraining from outputting alerts while the BWTD is on an aircraft mayreduce the number of false alerts, may advantageously reduce the burdenon computing resources of the BWTD and/or a receiving monitoring system,the amount of data transferred between the BWTD and monitoring system,and generally the number of notifications processed and provided to themonitored person and/or law enforcement. Reducing the number ofnotifications may improve processing efficiencies, and ease the burdenon monitored persons and/or law enforcement in assisting monitoredpersons to stay within permitted geographic boundaries. In someexamples, the BWTD may automatically disable one or more wirelesstransceivers (e.g., GPS device, cellular devices, etc.) in response todetermining that the BWTD is on board an aircraft, which may reduce thepower consumed by the BWTD and improve the battery life of the BWTD.

In an example, this disclosure describes a body-worn tracking device(BWTD) comprising: a global navigation satellite system (GNSS) device; acellular communication unit; at least one processor; and at least onememory device comprising instructions that, when executed by the atleast one processor, cause the at least one processor to: determinewhether the BWTD is located on board an aircraft; and responsive todetermining that the BWTD is located on board the aircraft: disable theGNSS device and the cellular communication unit; and temporarily refrainfrom generating an alert that indicates a current location of the BWTDcannot be determined.

In another example, this disclosure describes a method comprising:determining, by one or more processors, whether a body-worn trackingdevice (BWTD) is located on board an aircraft; and responsive todetermining that the BWTD is located on board the aircraft: disabling,by the one or more processors, a GNSS device of the BWTD and a cellularcommunication unit of the BWTD; and temporarily refraining, by the oneor more processors, from generating an alert that indicates a currentlocation of the BWTD cannot be determined.

The details of one or more examples are set forth in the accompanyingdrawings and the description below. Other features, objects, andadvantages of the disclosure will be apparent from the description,drawings, and claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a conceptual diagram illustrating an example monitoring systemfor determining a location of a body-worn tracking device, in accordancewith one or more aspects of this disclosure.

FIG. 2 is a perspective view of an example body-worn tracking device, inaccordance with one or more aspects of the present disclosure.

FIG. 3 is a block diagram illustrating example components of a body-worntracking device, in accordance with one or more aspects of the presentdisclosure.

FIG. 4 is a block diagram illustrating example components of a serverdevice, in accordance with one or more aspects of the presentdisclosure.

FIG. 5A includes a flow diagram illustrating example operations of amonitoring system, in accordance with aspects of this disclosure.

FIG. 5B includes a flow diagram illustrating example operations of amonitoring system, in accordance with aspects of this disclosure.

DETAILED DESCRIPTION

In an offender monitoring system, each offender is typically assigned adevice (e.g., a body-worn tracking device (BWTD)) that determines andstores a variety of data such as location, speed, heading, or the likeat prescribed intervals (e.g., every minute). The device typicallyincludes a Global Navigation Satellite System (GNSS) device (e.g., aGlobal Positioning System (GPS) receiver) to help determine when theoffender violates the terms of his or her parole (e.g., by enteringprohibited geographic areas or exiting permitted areas). However, GNSSdevices may temporarily be unable to receive signals from a sufficientnumber of GNSS satellites, for example, due to surrounding structure orenvironmental features. When the GNSS device of a BWTD does not receivesignals from a sufficient number of GNSS satellites, the BWTD may beunable to determine its current GNSS coordinates, which may limit theability of law enforcement to ensure the offender complies with theterms of his or her parole. An offender wearing a BWTD may also bereferred to as a monitored person or monitored target.

Typically, when a BWTD is unable to determine its GNSS coordinates, theBWTD and/or a monitoring system may generate an alert. For example, theBWTD may output a message or alert instructing the offender to proceedto an area where the GNSS coordinates can be determined (e.g., gooutside). The BWTD may output a message to a monitoring centerindicating that the BWTD is unable to determine its current GNSScoordinates. In some instances, the monitoring system may output anotification (e.g., to law enforcement personnel) indicating that theBWTD cannot determine its GNSS coordinates, which may indicate thatmonitored person is potentially in violation of his or her parole.

Certain types of vehicles (e.g., an aircraft, marine craft, train, etc.)may reduce or eliminate the ability of a BWTD to receive signals fromGNSS satellites (e.g., due to the shape, size, and/or materials of thevehicle), thus potentially preventing the BWTD from determining its GNSScoordinates when the BWTD is located in the vehicle. Because the BWTDmay be unable to determine its GNSS coordinates for an extended amountof time while traveling in certain vehicles (e.g., while on anaircraft), the monitored person assigned to wear the BWTD may beeffectively prohibited from traveling in certain vehicles. Thus,conventionally, should the monitored person attempt to travel viaaircraft (e.g., even to a destination to which the monitored person ispermitted to travel), the monitoring system and/or BWTD may erroneouslygenerate alerts indicating the monitored person is violation of his orher parole.

In accordance with various techniques of this disclosure, a monitoringsystem and/or BWTD may determine whether a BWTD, and hence a monitoredperson assigned to wear the BWTD, is located on board an aircraft andmay temporarily refrain from generating alerts while the BWTD is onboard the aircraft. Additionally, the monitoring system and/or BWTD maydetermine whether the aircraft is an aircraft the monitored person ispermitted to be on. Additionally or alternatively, the monitoring systemand/or BWTD may determine whether the destination of the aircraft is alocation to which the monitored person is permitted to travel. In otherwords, the monitoring system may determine whether the monitored personis on an aircraft and if so, where the aircraft is headed. The BWTD maycommunicate with the monitoring system via the aircraft's WiFi® networkduring flight to track the BWTD during the flight. Thus, in someexamples, the BWTD and/or monitoring system may refrain from generatingalerts to the monitored person and/or law enforcement personnel whilethe BWTD is on the aircraft. Refraining from outputting alerts while theBWTD is on the aircraft may reduce the number of false alerts, which mayreduce the amount of data transferred between the BWTD and monitoringsystem. Reducing the number of alerts may ease the burden on monitoredpersons and/or law enforcement in assisting monitored persons to staywithin permitted geographic boundaries. In some examples, the BWTD mayautomatically disable one or more wireless transceivers (e.g., GPSdevice, cellular radios, etc.) in response to determining that the BWTDis on board an aircraft, which may reduce the power consumed by the BWTDand improve the battery life of the BWTD.

FIG. 1 is a conceptual view illustrating an example monitoring system100 for determining a location of a body-worn tracking device, inaccordance with one or more aspects of this disclosure. Monitoringsystem 100 comprises a body-worn tracking device (BWTD) 106, satellites108A through 108N (collectively, “satellites 108”), a monitoring center112, a network 115, and a user device 116. People shown in the exampleof FIG. 1 are not considered part of monitoring system 100. A monitoredtarget 104 wears BWTD 106. Monitoring system 100 tracks the location ofBWTD 106, and thereby tracks the location of monitored target 104.Although not shown in the example of FIG. 1 for the sake of simplicity,monitoring system 100 may track the locations of multiple BWTDs, andthereby track the locations of multiple monitored targets.

In the example of FIG. 1, monitored target 104 and BWTD 106 are locatedwithin a geographic region 101, which may be a portion of the Earth'ssurface. In this example, geographic region 101 includes multiple roads102A-102C (“roads 102”) on which monitored target 104 may travel.Geographic region 101 may include human built structures (e.g., houses,buildings, and the like) and/or natural structures (trees, mountains,oceans, lakes, and the like).

In the example of FIG. 1, monitored target 104 is a person wearing BWTD106. However, in other examples, a monitored target may be a non-humanobject to which a BWTD is attached. For instance, a monitored target maybe an animate object (e.g., an animal, robot) or inanimate object thatmay move to different locations in a geographic area. In examples wherea monitored target is non-human, a BWTD may be any device that isattached to, accompanies or is otherwise physically associated with themovable object, even if not necessarily bodily worn.

Monitored target 104 may be a released criminal offender, although inother examples a monitored target may be any person. Released criminaloffenders may be criminal offenders who have been suspected, accused, orconvicted of a crime and released from a jail or prison. For instance,when monitored target 104 is released from jail, prison, or otherfacility, BWTD 106 may be attached by law enforcement to the body ofmonitored target 104. In some examples, monitored target 104 is anindividual with certain a psychological condition, such as dementia orAlzheimer's disease, that makes the individual likely to leave safeareas. In such examples, a caregiver may use BWTD 106 to monitor thelocation of such an individual.

BWTD 106 may comprise a portable computing device that determines itscurrent location and reports the determined location to monitoringcenter 112 or another physically separate computing device. Furthermore,BWTD 106 may include a physical housing constructed of plastic or anyother suitable material. The housing may include electronics such as,but not limited to: one or more computer processors, one or more memorydevices, one or more wired and/or wireless communication devices (e.g.,cellular network component, WiFi® component, short-range (e.g., a NearField Communication (NFC) component, a Bluetooth component, a UniversalSerial Bus (USB) component), one or more output devices (e.g., a hapticfeedback component, one or more lights, one or more user interfacedisplay components, one or more audio components), one or more GNSScomponents (e.g., a GPS receiver), one or more sensor components (e.g.,an accelerometer, a gyroscope, a magnetometer, a barometer, etc.), oneor more power sources (e.g., battery, power supply), and one or morecircuit boards that physically, communicatively, and/or electronicallycouple such components to one another within the housing of BWTD 106.

Each respective satellite of satellites 108 transmits a respectivesatellite signal indicating a current time and a current location of therespective satellite. BWTD 106 may include a combination of software andhardware components to receive the satellite signals transmitted bysatellites 108. In some examples, satellites 108 are global navigationsatellites in a global navigation satellite system (GNSS). Exampleglobal navigation satellite systems include the GPS satellite network,the Galileo satellite network, the GLONASS satellite network, and othergovernment-operated or commercially-operated satellite networks. Eachsatellite signal received by BWTD 106 from a satellite of satellites 108includes data such as the current position of the particular satelliteand the current time. Although the example of FIG. 1 only shows threesatellites, different numbers of satellites may be used by BWTD 106 todetermine the GNSS coordinates of BWTD 106 at a point in time.

In some examples, BWTD 106 is a one-piece design in which GNSS hardwareand all other hardware for the BWTD are included in a single physicalhousing. In other examples, BWTD 106 may not include GNSS hardware,which may be physically separate from, but in communication with, BWTD106. For instance, monitored target 104 may carry a physical device withGNSS hardware (e.g., such as a computing device 107 having GNSSfunctionality), and separately BWTD 106 may be attached to monitoredtarget 104 and in communication with computing device 107. Computingdevice 107 may include a laptop computer, a tablet computer, asmartphone, a desktop computer, a server computer, a body worn computer(e.g., smartwatch, head-mounted device), or any other suitable computingdevice. Computing device 107 may be configured to interface with BWTD106 to provide the functionality described herein with respect to BWTD106.

In some examples, BWTD 106 may further include a combination of softwarecomponents and hardware components to perform one or more monitoringfunctions. For example, BWTD 106 may determine and record GNSScoordinates of BWTD 106. For instance, BWTD 106 may receive data fromsatellites 108 (e.g., data indicative of the position of a particularsatellite) and may determine GNSS coordinates of BWTD 106 based on thedata received from satellites 108. In some examples, BWTD 106 sends itsGNSS coordinates to monitoring center 112 or other physically separatecomputing device.

BWTD 106 includes one or more sensor components that detects movement ofBWTD 106. The sensor components may include hardware or a combination ofhardware and software. In some examples, the one or more sensorcomponents include an accelerometer, one or more directionality sensors(e.g., a gyroscope, a magnetometer, and/or other sensors for determininga spatial orientation), and so on. BWTD 106 may receive accelerationdata from the accelerometer that indicates amounts of accelerationvarious axes, such as a vertical axis and a horizontal axis. BWTD 106may determine a change in the orientation (e.g., direction) of BWTD 106for each step based on orientation data received from the directionalitysensor (e.g., the gyroscope and/or the magnetometer). BWTD 106 maydetermine the direction of BWTD 106 relative to Earth's magnetic fieldbased on data received from the magnetometer.

BWTD 106 may have a unique device identifier that is different fromunique identifiers of each other BWTD in a set of BWTDs. In this way, asmonitored target 104 moves to different locations in a geographicregion, geographic location points generated by BWTD 106 and stored atmonitoring center 112 may be associated with or otherwise attributed tomonitored target 104, such that the location and/or whereabouts ofmonitored target 104 may be monitored.

Monitoring system 100 may also include one or more towers, such as tower110, that form cellular network infrastructure. Tower 110 may include aphysical structure that supports antennae, a GNSS receiver, one or moresets of digital signal processors, transceivers, and controlelectronics, which collectively operate to establish sessions withend-user devices such as BWTDs, smartphones, or other computing devices.Tower 110, together with one or more other towers that include similarfunctionality, may be geographically dispersed, so as to provide ageographically dispersed wireless network for voice and/or datacommunication. Tower 110 and switching infrastructure (not shown) may beowned and operated by wireless or cellular carrier providers that chargecustomer/subscriber fees to operate on the wireless or cellular carrierprovider.

Monitoring center 12 may be owned and operated by a private entity or agovernment entity. Monitoring center 112 includes one or more computingdevices, such as server devices 114A-114N (“server devices 114”). Asdescribed elsewhere in this disclosure, FIG. 4 illustrates details ofexample components of server devices 114. Server devices 114 maycollectively provide a data center to monitor and track monitoredpersons based on, among other data, GNSS coordinates of BWTDs that areprovided to server devices 114.

In some examples, server devices 114 stores an association between amonitored person and a respective BWTD worn by a monitored target. Forinstance, at the time that a BWTD is attached to the monitored target, auser may use a separate, end-user computing device in communication withmonitoring center 112 to provide user input that creates an associationbetween a unique identifier of the monitored target and a uniqueidentifier of the BWTD. For instance, the association may be stored as arecord in a database. Responsive to receiving GNSS coordinates from theBWTD with a unique identifier of BWTD 106, monitoring center 112 maystore the GNSS coordinates in association with the unique identifier ofBWTD 106. In this way, an operator of monitoring center 112 maydetermine the GNSS coordinates associated with monitored target 104.

Monitoring center 112 may receive configuration input from users, suchas law enforcement officers, that defines authorized and/or unauthorizedtravel for monitored target 104. Such configuration input may be sent bya computing device (e.g., user device 116) to monitoring center 112 vianetwork 115. The configuration input may specify a unique identifier ofmonitored target 104 and/or BWTD and may also include informationindicating permitted travel for monitored target 104. For instance, thepermitted travel information may include permitted modes of travel(e.g., a general mode such as “car” or “plane”), permitted traveldates/times, permitted destinations, or other information indicatingwhen, where, or how monitored target 104 is permitted to travel. In someinstances, the permitted travel information includes flight information,such as an airline and/or flight number of a flight upon which monitoredtarget 104 is permitted to travel, departure airport, destinationairport, etc.

In some examples, the permitted travel information includes informationreceived from a travel provider (e.g., airline). For example, monitoringcenter 112 may interface with an airline computing system and mayreceive information about a particular flight. For instance, amonitoring user 118 may approve monitored target 104 to travel on aparticular airline and flight and may save a flight number for thepermitted flight to monitoring center 112. Monitoring center 112 mayquery a remote computing system (e.g., operated by a travel provider)for additional flight information such as a departure location,departure date/time, arrival location, arrival date/time, or anyinformation associated with the permitted flight. In some instances,monitoring center 112 receives (e.g., from a travel provider) flightinformation, such as information indicative of a wireless network onboard a given flight, such as a network service set identifier (SSID) ormedia access control (MAC) address of a networking device on board apermitted flight).

In this way, monitoring center 112 may associate permitted travelinformation with BWTD 106 and/or monitored target 104. By associatingpermitted travel information with BWTD 106 and/or monitored target 104,monitoring center 112 can determine violations, such as, determiningwhether a monitored person is traveling via a permitted method oftransportation, traveling on a permitted day/timeframe, and/or travelingto a permitted destination.

In some examples, BWTD 106 and/or monitoring center 112 may determinethat a monitored target 104 is traveling and that the travel is inviolation of permitted travel plans. In response to detecting aviolation, BWTD 106 and/or monitoring center 112 may send a notificationor output an alert indicative of the violation. For instance, monitoringcenter 112 may send a notification via network 115 to BWTD 106 for theviolation, which may cause BWTD 106 to output an alert (e.g., haptic,visual, and/or audio feedback). In some examples, monitoring center 112may send notifications to one or more monitoring users 118 (e.g., lawenforcement personnel) that monitored person 104 is potentially inviolation of his or her parole.

Monitoring center 112 may generate user interfaces for display, such asmaps that indicate different locations at which BWTD 106 has beenphysically present. In some examples, monitoring center 112 mayillustrate different locations at which BWTD 106 has been physicallypresent over a period of time. Monitoring center 112 may output any datathat in any suitable format including still and moving image data, audiodata, and the like. For instance, geographic region 101 may be visuallyrepresented in a map, which may be two- or three-dimensional. Such mapsmay be output for display by computing devices as further described inthis disclosure. In the example of FIG. 1, a map generated based ongeographic region 101 may be visually similar in appearance to therepresentation of geographic region 101 as illustrated in FIG. 1.

In the example of FIG. 1, monitoring user 118 uses user device 116.Although FIG. 1 shows user device 116 as a smartphone, user device 116may be various types of computing device. For example, user device 116may be a laptop computer, a tablet computer, a smartphone, a desktopcomputer, a server computer, a body worn computer (e.g., smartwatch,head-mounted device), or any other suitable computing device. Althoughthe example of FIG. 1 shows monitoring system 100 as only including asingle user device 116, monitoring system 100 may comprise multiple userdevices performing functions similar to user device 116.

User device 116 may include one or more components comprising acombination of hardware and software. For instance, user device 116 mayexecute a monitoring application implemented in software and executableon hardware of user device 116. The monitoring application may providenotifications of violations, maps or other visual representations ofmonitored offender locations based on real-time or past-generated GNSScoordinates. The monitoring application may also generate and send datathat associates a unique identifier of BWTD 106 with a unique identifierof monitored target 104. In some examples, the monitoring applicationmay natively implement functionality described in this disclosure, whilein other examples the monitoring application may be a web-browser thataccesses a web-based application with such functionality via aweb-hosted application executing at monitoring center 112.

Monitoring user 118 may be a law enforcement officer, parole officer, oranother type of public safety official or employee. In some examples,monitoring user 118 is a non-public safety office/employee, such as pastor potential victims of a monitored offender, a school administrator, oranother type of user that may be interested in or need to know of thelocation or violations of a monitored target. User device 116 mayprovide notifications to monitoring user 118 in response to messagessent by monitoring center 112.

Network 115 may represent a publicly accessible computer network that isowned and operated by a service provider, which is usually largetelecommunications entity or corporation. Although not illustrated inthe example of FIG. 1, network 115 may be coupled to one or morenetworks administered by other providers, and may thus form part of alarge-scale public network infrastructure, e.g., the Internet. Network115 may provide computing devices, such as BWTD 106, user device 116,and monitoring center 112, with access to the Internet, and may allowthe computing devices to communicate with each other. In some examples,network 115 may include one or more local area networks (LANs), suchthat user device 116 may communicate with monitoring center 112 throughthe Internet and/or a LAN on which both monitoring center 112 and userdevice 116 are included.

Although additional network devices are not shown in the example of FIG.1 for ease of explanation, it should be understood that network 115 andmonitoring system 100 may comprise additional network and/or computingdevices such as, for example, one or more additional switches, routers,hubs, gateways, security devices such as firewalls, intrusion detection,and/or intrusion prevention devices, servers, computer terminals,laptops, printers, databases, wireless mobile devices such as cellularphones or personal digital assistants, wireless access points, bridges,cable modems, application accelerators, or other network devices. Itshould be understood that one or more additional network elements may beincluded along any of network links 120A, 120B, and 120C (collectively,“network links 120”), such that the devices of monitoring system 100 arenot directly coupled. Network links 120 may be wired or wirelesscommunication links, such as 100 Mbps, 1 Gbps, or 10 Gbps WiFiconnections and/or physical cable connections, to name only a fewexamples.

To monitor a location of monitored target 104, BWTD 106 may be attachedto monitored target 104. In some examples, BWTD 106 includes atamper-resistant strap that binds BWTD 106 to monitored target 104. BWTD106 may include one or more components comprised of hardware and/orsoftware that detect if monitored target 104 or another person havetampered with the tamper-resistant strap and/or the housing/internalcomponents of BWTD 106. If BWTD 106 detects that a tampering event isoccurring or has occurred, BWTD 106 may send a message via network 115to monitoring center 112 to indicate the tampering event.

User device 116 may receive indications of user input from monitoringuser 118 that define an association between BWTD 106 and monitoredtarget 104 in monitoring center 112. In other words, monitored target104 may be assigned to wear BWTD 106. User device 116, for example, mayoutput a graphical user interface for display. The graphical userinterface may include one or more user interface components, such asinput fields, dropdown menus, labels or text fields, or any othergraphical component through which BWTD 106 may receive indications ofuser input from monitoring user 118.

In the example of FIG. 1, user device 116 may receive indications ofuser input from monitoring user 118 that specify or select a uniqueidentifier of BWTD 106 and may further receive one or more user inputsfrom monitoring user 118 that specify or select a unique identifier ofmonitored target 104. In addition to receiving an indication of userinput specifying or selecting the unique identifiers of BWTD 106 and/ormonitored target 104, user device 116 may receive input from monitoringuser 118 to define an association between the respective uniqueidentifiers. User device 116 may send one or more messages to monitoringcenter 112 that define the association between the unique identifier ofmonitored target 104 and BWTD 106.

In some examples, user device 116 may receive indications of user inputdefining information associated with permitted travel for a monitoredtarget 104 assigned to wear BWTD 106. For example, user device 116 mayreceive an indication of user input defining a permitted traveldestination, permitted travel timeframe (e.g., permitted flight datesand/or times), permitted methods of travel (e.g., a permitted flightnumber), or any combination therein. User device 116 may send one ormore messages to monitoring center 112 with the permitted travelinformation as specified by monitoring user 118, and monitoring center112 may configure or associate the permitted travel information with theunique identifier of monitored target 104 and BWTD 106.

After BWTD 106 has been attached to monitored target 104, monitoredtarget 104 may be released from custody (e.g., released from a confinedor restricted condition, such as a jail, prison, or courthouse). Asmonitored target 104 moves throughout a geographic region, such asgeographic region 101, BWTD 106 determines respective GNSS coordinatesof BWTD 106 and sends messages to monitoring center 112 that may includeat least a unique identifier of BWTD 106 and/or monitored target 104,unique tower identifier, GNSS coordinates (latitude, longitude), andtimestamps for when each respective GNSS coordinate has been determined.BWTD 106 may wirelessly communicate such messages to tower 110, which inturns sends the messages to monitoring center 112 via network 115, andin some examples one or more additional, intermediate networked devices(not shown in FIG. 1).

In accordance with techniques of this disclosure, a computing device(e.g., BWTD 106 and/or one or more server devices 114) may determinewhether BWTD 106 is located on board an aircraft. In some examples, BWTD106 may determine whether BWTD 106 is located onboard an aircraft basedat least in part on data generated by one or more sensors of BWTD 106.In some examples, an accelerometer of BWTD 106 detects acceleration ofan aircraft while the aircraft taxis from a gate to a runway, and downthe runway during the takeoff maneuver. BWTD 106 may determine that BWTD106 is located on board an aircraft by comparing the detectedacceleration to a template acceleration pattern corresponding to anaircraft take-off. For example, the template acceleration patterncorresponding to an aircraft take-off may be characterized by a largeinitial acceleration in a horizontal plane over a first time-period(e.g., when a pilot initially engages a motor to generate thrust). Thetemplate acceleration pattern may include a relatively constantacceleration over a second time-period after the initial period of time(e.g., five, ten, thirty seconds, or more) that is indicative of anaircraft increasing speed during takeoff. In some examples, BWTD 106determines that BWTD 106 is located on board an aircraft in response todetermining that a portion of the acceleration data generated by anaccelerometer of BWTD 106 corresponds to the shape of the templateacceleration pattern.

In some examples, BWTD 106 determines whether BWTD 106 is on board anaircraft based at least in part on a non-cellular wireless networkconnection between BWTD 106 and a wireless communication device on boardthe aircraft. For example, BWTD 106 may receive a message (e.g., frommonitoring center 112) indicating permitted travel information, such asflight information associated with a permitted flight (e.g., a flightnumber, airline, and/or flight dates and times). In some instances, thepermitted flight information indicates a wireless communication deviceon board an aircraft flying the permitted flight. For instance, thepermitted flight information may include a wireless network identifier(e.g., a network SSID on board the aircraft) or a networking deviceidentifier (e.g., a MAC address of a networking device on board theaircraft) associated with the permitted flight.

In some instances, BWTD 106 may detect one or more wireless networks andmay compare a network identifier (e.g., SSID) or device identifier(e.g., MAC address) associated with a detected wireless network to thereceived flight information (e.g., network identifier or networkingdevice identifier associated with the permitted flight). For instance,BWTD 106 may determine that BWTD 106 is on board an aircraft in responseto determining the network identifier (e.g., SSID) of an availablenetwork matches the network identifier of the expected networkidentifier associated with a permitted flight. Similarly, BWTD 106 maydetermine that BWTD 106 is on board an aircraft in response todetermining that a device identifier (e.g., MAC address) correspondingto an available network matches the networking device identifier of theexpected networking device associated with the permitted flight. Inother words, BWTD 106 may determine that BWTD 106 is located on board anaircraft in response to determining that an available non-cellularwireless network corresponds to a predetermined non-cellular wirelessnetwork expected to be available on board an aircraft flying a permittedflight.

In response to determining that BWTD 106 is located on board anaircraft, BWTD 106 may disable the GNSS device of BWTD 106. Forinstance, the GNSS device may not be able to determine the GNSScoordinates of BWTD 106 when BWTD 106 is located on board an aircraft,such that BWTD 106 may disable the GNSS device while BWTD 106 is onboard the aircraft. Disabling the GNSS device while BWTD 106 is locatedon board the aircraft may reduce the battery consumed by the GNSSdevice, thus potentially increasing the battery life of the BWTD 106.

BWTD 106 may refrain from generating alerts when BWTD 106 is located onboard the aircraft. For instance, in response to determining that BWTD106 is located on board the aircraft, BWTD 106 may temporarily refrainfrom generating alerts that indicate BWTD 106 cannot determine its GNSScoordinates using the GNSS device. In other words, BWTD 106 may refrainfrom alerting the monitored person 104, monitoring center 112, and/oralerting law enforcement personnel that BWTD 106 is not connected toenough GNSS satellites to determine its GNSS coordinates. By refrainingfrom generating alerts indicating that BWTD 106 cannot determine itsGNSS coordinates when BWTD 106 is located on board an aircraft, BWTD 106may reduce the network traffic between BWTD 106 and monitoring center112 and may reduce the processing performed by BWTD 106 and/ormonitoring center 112. Refraining from generating alerts when BWTD 106is located on board an aircraft may enable monitored person 104 totravel via vehicles that may prevent BWTD 106 from receiving signalsfrom GNSS satellites and may reduce the number of false alerts. Reducingthe number of alerts may also reduce the time and resources consumed bylaw enforcement personnel in supervising monitored persons.

While the techniques described herein are described in the context ofdetermining whether a BWTD is located on board an aircraft, techniquesof this disclosure may also be used to determine whether a BWTD islocated within other permitted areas even if the BWTD is unable todetermine its GNSS coordinates in that permitted area. For example, BWTD106 may lose a connection to one or more GNSS satellites upon movingindoors, below ground, or any other location where satellite signals areobstructed by topography or man-made or naturally occurring structures.For instance, BWTD 106 may be unable to determine its GNSS coordinateswhen monitored person 104 is at his or her place of employment. In somescenarios, BWTD 106 may determine that BWTD 106 is located in apermitted area based on a network identifier of a wireless (e.g., WiFi®)network and/or a device identifier (e.g., MAC address) for a networkingdevice (e.g., a router) at the place of employment of monitored person106. Thus, BWTD 106 may refrain from generating alerts when BWTD 106 islocated within a known, permitted area.

FIG. 2 is a perspective view of an example BWTD, in accordance with oneor more aspects of the present disclosure. BWTD 106 may be configured toimplement various aspects of this disclosure. FIG. 2 illustrates onlyone particular example of BWTD 106, as shown in FIG. 1. Many otherexamples of BWTD 106 may be used in other instances. Other BWTDs mayinclude different subsets of the components than those of the example ofBWTD 106 shown in FIG. 2. As illustrated in FIG. 2, BWTD 106 may beattached to an ankle 212 of monitored target 104. Furthermore, asillustrated in FIG. 2, BWTD 106 includes a strap 214 and a housing 216.Housing 216 includes a variety of components such as one or moreprocessors configured to perform the techniques described herein, one ormore storage components for storing instructions executable by theprocessor along with data, one or more GNSS components, one or moresensors, and one or more communication units. The one or morecommunication units may enable BWTD 106 to communicate wirelessly withan external device.

FIG. 3 is a block diagram illustrating example components of BWTD 106,in accordance with one or more aspects of the present disclosure. FIG. 3illustrates only one particular example of BWTD 106, as shown in FIG. 1or FIG. 2. Many other examples of BWTD 106 may be used in otherinstances and may include a subset of the components included in BWTD106 or may include additional components not shown in FIG. 3. In someexamples, the external housing (not shown) of BWTD 106 may have one ormore attachment components (not shown), such as straps, fasteners,magnetic materials, adhesive materials or any other mechanism ormaterial for attaching or associating with tracking device 106A with anobject to be tracked.

As shown in the example of FIG. 3, BWTD 106 may be logically dividedinto control environment 302 and hardware 328. Hardware 328 may includeone or more hardware components that provide an operating environmentfor components executing in control environment 302. Control environmentmay include control logic 304, data 308, and operating system 324, whichmay be operable by processors 330 to perform various functions describedherein. In some instances, operating system 324 may operate with higherprivileges than other components executing in control environment 302.

As shown in FIG. 3, hardware 328 includes one or more processors 330,input components 332, power source 334, storage components 338,communication units 340, output components 342, GNSS components 343, andsensor components 344. Processors 330, input components 332, powersource 334, storage components 338, communication units 340, outputcomponents 342, GNSS components 343, and sensor components 344 may eachbe interconnected by one or more communication channels 336.Communication channels 336 may interconnect each of components 330, 332,334, 338, 340, 342, 343, and 344 for inter-component communications(physically, communicatively, and/or operatively). In some examples,communication channels 336 may include a hardware bus, a networkconnection, one or more inter-process communication data structures, orany other components for communicating data between hardware and/orsoftware.

One or more processors 330 may implement functionality and/or executeinstructions within BWTD 106. For example, processors 330 on BWTD 106may receive and execute instructions stored by storage components 338that provide the functionality of components included in controlenvironment 302. These instructions executed by processors 330 may causeBWTD 106 to store and/or modify information, within storage components338 during program execution. Processors 330 may execute instructions ofcomponents in control environment 302 to perform one or more operationsin accordance with techniques of this disclosure. That is, componentsincluded in control environment 302 may be operable by processors 330 toperform various functions described herein.

One or more input components 332 of BWTD 106 may receive input. Examplesof input are tactile, audio, kinetic, and optical input, to name only afew examples. Input components 332 of BWTD 106, in one example, includea voice responsive system, video camera, buttons, control pad,microphone or any other type of device for detecting input from a humanor machine. In some examples, input component 332 may be apresence-sensitive input component, which may include apresence-sensitive screen, touch-sensitive screen, etc.

As shown in FIG. 3, BWTD 106 may include a power source 334. In someexamples, power source 334 is a battery. Power source 334 provides powerto one or more components of BWTD 106. Examples of power source 334include, but are not necessarily limited to, batteries havingzinc-carbon, lead-acid, nickel cadmium (NiCd), nickel metal hydride(NiMH), lithium ion (Li-ion), and/or lithium ion polymer (Li-ionpolymer) chemistries. In some examples, power source 334 may have alimited capacity (e.g., 1000-3000 mAh).

One or more storage components 338 within BWTD 106 may store informationfor processing during operation of BWTD 106. In some examples, storagecomponents 338 include a temporary memory, meaning that a primarypurpose of storage components 338 is not long-term storage. Storagecomponents 338 on BWTD 106 may configured for short-term storage ofinformation as volatile memory and therefore not retain stored contentsif deactivated. Examples of volatile memories include random accessmemories (RAM), dynamic random access memories (DRAM), static randomaccess memories (SRAM), and other forms of volatile memories known inthe art.

Storage components 338, in some examples, also include one or morecomputer-readable storage media. Storage components 338 may beconfigured to store larger amounts of information than volatile memory.Storage components 338 may further be configured for long-term storageof information as non-volatile memory space and retain information afteractivate/offcycles. Examples of non-volatile memories include magnetichard discs, flash memories, or forms of electrically programmablememories (EPROM) or electrically erasable and programmable (EEPROM)memories. Storage components 338 may store program instructions and/ordata associated with components included in control environment 302.

One or more output components 342 of BWTD 106 generate output. Examplesof output are tactile output (e.g., haptic output, vibratory output),audio output, and video output. Output components 342 of BWTD 106, insome examples, include a display screen, a presence-sensitive screen, asound card, a video graphics adapter card, a speaker, a liquid crystaldisplay (LCD), or another type of device for generating output to ahuman or machine. In some examples, output components 342 are integratedwith BWTD 106 and physically connected to the external packaging of BWTD106. In other examples, output components 342 are physically external toand separate from BWTD 106, but are operably coupled to BWTD 106 viawired or wireless communication.

One or more communication units 340 of BWTD 106 communicate withexternal devices by transmitting and/or receiving data. For example,BWTD 106 may use communication units 340 to transmit and/or receiveradio signals on a radio network such as a cellular radio network ornon-cellular radio network. Communication units 340 may include cellularcommunication units 352 and non-cellular communication units 354.Examples of cellular communication units 352 include 2G, 3G, 4G, CDMA,GSM, and LTE radios. Examples of non-cellular communication units 354include a network interface card (e.g. such as an Ethernet card), anoptical transceiver, a radio frequency transceiver, or any other type ofdevice that can send and/or receive information. Other examples ofnon-cellular communication units 354 include Bluetooth® and Wi-Fi®radios as well as Universal Serial Bus (USB) controllers and the like.

GNSS components 343 receive satellite signals from GNSS satellites(e.g., satellites 108 (FIG. 1)). Location detection component 312 maydetermine, based on the received satellite signals, coordinatescorresponding to a location of BWTD 106 at a particular point in time.

In some examples, sensor components 344 include a plurality of sensingcomponents, such as accelerometer components 346, gyroscope components348, and altimeter components 350. Accelerometer components 346 maygenerate data indicative of the acceleration of BWTD 106 in at least oneplane. In some examples, accelerometer components 346 include a 3-axisaccelerometer that detects acceleration in 3-dimensions and generatesdata indicative of the acceleration in each of the 3-dimensions.Gyroscope components 348 may generate data indicative of a change in theorientation (e.g., direction) of BWTD 106 in one or more of the3-dimensions. As illustrated in FIG. 3, sensor components 344 mayinclude altimeter components 350. Altimeter components 350 may detectthe air-pressure and may generate data indicative of the detectedair-pressure.

In the example of FIG. 3, control logic 304 executes in controlenvironment 302. Control logic 304 may include but is not limited to: adevice management component (DMC) 308, a communication component 310, alocation detection component 312, a notification component 314, and atravel detection component 315. In some examples, BWTD 106 may run aset, subset, or superset of functionality included in control logic 304.Data 306 may include one or more data stores. A data store may storedata in structured or unstructured form. Example data stores may be anyone or more of a relational database management system, onlineanalytical processing database, table, or any other suitable structurefor storing data. In the example of FIG. 3, data 306 includesconfiguration data 316, tower data 318, location data 320, and rule data322. Storage components 338 may store data 306.

Components such as DMC 308, communication component 310, locationdetection component 312, notification component 314, and traveldetection component 315 may perform operations described herein usingsoftware, hardware, firmware, or a mixture of both hardware, software,and firmware residing in and executing on BWTD 106. In some examples,processors 330 of BWTD 106 may execute various components when embodiedin software to perform the functionality described in this disclosure.Processors 330 may execute any of such components as or within a virtualmachine, user space application, operating system or any other operatingenvironment executing on underlying hardware.

Configuration data 316 may include one or more of: a unique identifierof BWTD 106, a unique identifier of the monitored person to which BWTD106 is assigned, and/or any other properties or parameters that controlor change the operation of tracking device 106A. Tower data 318 mayinclude records, tuples or sets, wherein each record, tuple or setspecifies one or more of: a unique identifier of a particular tower, alatitude and longitude of BWTD 106 when BWTD 106 detected or initiated acommunication session with the particular tower, a signal strength forthe tower when BWTD 106 detected or initiated a communication sessionwith the particular tower, a directional heading of BWTD 106 when BWTD106 detected or initiated a communication session with the particulartower, and/or a timestamp when BWTD 106 detected or initiated acommunication session with the particular tower.

Location data 320 may include records, tuples or sets, wherein eachrecord, tuple or set specifies one or more of: a unique identifier ofBWTD 106 and/or a monitored person wearing BWTD 106, GNSS coordinates(e.g., latitude, longitude), a timestamp when the GNSS coordinates weredetermined, GNSS signal strength when the GNSS coordinates weredetermined, signal strength of a tower when the GNSS coordinates weredetermined, and/or a directional heading of BWTD 106 when the GNSScoordinates were determined.

Rule data 322 may include permitted flight information, such as theairline, flight number, flight destination, expected departuredate/time, expected arrival date/time, expected travel duration, orother flight information corresponding to a flight (or other form ofpermitted transportation) that a monitored target is permitted to travelupon. Rule data 322 may include permitted flight information formultiple travel legs. For instance, rule data 322 may include flightinformation for a flight from a city of origin to a destination city, aflight from a city of origin to a temporary destination (e.g., due to aflight layover) and a flight from the temporary destination to a finaldestination), and/or a return flight from the destination to the city oforigin. Rule data 322 may indicate one or more aircraft corresponding toa permitted flight. For instance, rule data 322 may include an aircraftregistration number (e.g., a unique aircraft identifier) associated witha particular flight code (or flight number), aircraft manufacturer,aircraft model, etc. In some instances, rule data 322 includesnetworking information (e.g., a wireless network identifier, such as anSSID; or a networking device identifier, such as a MAC address)corresponding to a wireless network expected to be available on boardthe aircraft flying a permitted flight. In some examples, rule data 322may include updated information corresponding to a permitted flight. Forexample, an aircraft designated to fly a permitted flight may betemporarily unavailable prior to takeoff (e.g., due to unplannedmaintenance) or an aircraft may be re-routed mid-flight (e.g., due toweather) such that BWTD 106 may receive updated flight information andmay receive flight information for the permitted flight.

In operation, DMC 308 may initially be configured with configurationdata 316. For instance, DMC 308 may be programmed, from an externalcomputing device, with a unique identifier for BWTD 106 and/or a uniqueidentifier of the monitored person associated with or assigned to BWTD106. Once BWTD 106 has been configured with configuration data 316, themonitored person may move about one or more geographic regions.Additionally, DMC 308 may write data to storage components 338 that isreceived from monitoring center 112 or other computing devices. Data mayinclude restricted regions and/or restricted locations, configurationdata to configure one or more components of BWTD 106, information thatuniquely identifies BWTD 106 and/or monitored target 104 that is wearingBWTD 106, or any other suitable information.

Communication component 310 maintains communication between BWTD 106 andmonitoring center 112. Communication component 310 may initiate, manage,and terminate communication sessions with towers that provide cellularnetwork infrastructure via cellular communication units 352. Forexample, as BWTD 106 moves to different geographic regions,communication component 310 may initiate communication sessions withdifferent towers in the different regions, where a tower may be a BaseStation Transceiver in a wireless communication network, such as acellular network. Examples of such cellular networks may include a setof one or more geographically dispersed towers with radios, antennasand/or other communications components that provide for datacommunication with BWTD 106 using one or more protocols such as 2G, 3G,4G, Long-Term Evolution (LTE), or any other suitable protocol. Cellularnetwork infrastructure may provide a wireless network for datacommunication to and from BWTD 106 over a geographically distributedarea. In some examples, cellular network infrastructure may be owned andoperated by a third-party, wireless or cellular carrier provider.Communication component 310 may manage communications with monitoringcenter 112 via non-cellular communication units 354. For example,communication component 310 may send message to, and receive messagesfrom, monitoring center 112 via a wired or wireless work (e.g., Wi-Fi®).

Location detection component 312 may determine the location (e.g., GNSScoordinates) of BWTD 106 based on data received from GNSS components343. For instance, GNSS components 343 may receive GNSS signals from aplurality of GNSS satellites (e.g., satellites 108 in FIG. 1). The GNSSsignals received from each GNSS satellite may include data indicating aposition of a respective GNSS satellite and a time at which therespective GNSS satellite sent the GNSS signal. Location detectioncomponent 312 may determine the latitude and longitude of BWTD 106 at aparticular point time based on the data received from the GNSSsatellites. Location detection component 312 may determine the latitudeand longitude on a periodic basis according to an interval that may beincluded in configuration data 316. The time interval may be programmedby a user, dynamically changed (e.g., based on one or more detected ordetermined events) or hard-coded. At a point in time (e.g., when a timeinterval has elapsed), upon determining the latitude and longitude,location detection component 312 may generate and store a record, tupleor set that specifies one or more of: a unique identifier of BWTD 106and/or monitored person wearing BWTD 106, GNSS coordinates (latitude,longitude), a timestamp when the GNSS coordinates (latitude, longitude)were determined, GNSS signal strength when the GNSS coordinates(latitude, longitude) were determined, signal strength of a tower whenthe GNSS coordinates (latitude, longitude) were determined, and/or adirectional heading of BWTD 106 when the GNSS coordinates (latitude,longitude) were determined. Location detection component 312 may sendlocation data 320 to monitoring center 112 of FIG. 1 in real-time,periodically, or asynchronously.

In some circumstances, location detection component 312 is unable todetermine the current location of BWTD 106. For example, GNSS components343 may be unable to receive GNSS signals from a sufficient number ofsatellites 108 (FIG. 1) such that location detection component 312 isunable to determine the geospatial location (e.g., GNSS coordinates) ofBWTD 106. For instance, GNSS components 343 may be unable to detect GNSSsignals from a sufficient number of GNSS satellites when BWTD 106 entersa building or enters a geographical area obstructed by manmade ornaturally occurring environmental features.

Notification component 314 may receive notifications from externalcomputing devices such as monitoring center 112 and/or user devices 116,as shown in FIG. 1. Notification component 314 may generate and sendnotifications to one or more external computing devices such asmonitoring center 112 and/or user devices 116.

Notifications generated by notification component 314 may be based oninput from travel detection component 315 and/or location detectioncomponent 312. In some examples, if location detection component 312 isunable to determine the current GNSS coordinates of BWTD 106,notification component 312 may generate a notification indicating thatthe current coordinates of BWTD 106 are unknown and may send thenotification to a computing device 107 associated with monitored target104 and/or monitoring center 112.

In accordance with techniques of this disclosure, BWTD 106 may refrainfrom generating notifications or alerts in response to determining thatBWTD 106 is on board a permitted vehicle. For example, travel detectioncomponent 315 may determine whether BWTD 106 is located on board anaircraft and may cause notification component 314 to temporarily refrainfrom outputting notifications in response to determining that BWTD 106is on board an aircraft (e.g., even if location detection component 312is unable to determine the current GNSS coordinates of BWTD 106).

BWTD 106 may determine whether BWTD 106 is located on board an aircraftbased on one or more sensor components 344. In some examples,accelerometer components 346 detects acceleration of the aircraft duringthe takeoff maneuver. Travel detection component 315 may determine thatBWTD 106 is located on board an aircraft by comparing the detectedacceleration to a template acceleration pattern corresponding to anaircraft take-off. In some examples, travel detection component 315determines that BWTD 106 is located on board an aircraft in response todetermining that at least a portion of the acceleration data generatedby accelerometer components 346 corresponds to the shape of the templateacceleration pattern.

In some examples, travel detection component 315 determines whether BWTD106 is on an aircraft based at least in part on the speed of BWTD 106.For instance, travel detection component 315 may integrate theacceleration data over a period of time to determine the speed of BWTD106. In some instances, travel detection component 315 may compare thespeed of BWTD 106 to a threshold speed. The threshold speed maycorrespond to an aircraft takeoff speed (e.g., approximately 150 mph or240 km/h for a commercial jetliner). In some instances, the thresholdspeed may correspond to an aircraft cruising speed (e.g., approximately500 mph or 800 km/h, or other speed fast enough that is not likelyachieved by other means of accelerating a BWTD, such as an automobile).Travel detection component 315 may determine that BWTD 106 is located onboard an aircraft in response to determining that the speed of BWTD 106satisfies (e.g., is greater than or equal to) the threshold speed.

Travel detection component 315 may determine whether BWTD 106 is onboard an aircraft based at least in part on the air pressure around BWTD106. For example, altimeter components 350 may generate pressure dataindicative of the air pressure. Travel detection component 315 maycompare the pressure of the air around BWTD 106 to the ground airpressure at the last known location of BWTD 106. For instance, the airpressure at sea level may be approximately 1 atmosphere (“ATM”), whichis approximately 101 kilopascals (kPa) or approximately 14.7 PSI. Incontrast, an aircraft at cruising altitude may be pressurized betweenapproximately 11 and approximately 12 PSI (approximately 0.75 toapproximately 0.80 ATM). Thus, travel detection component 315 maydetermine that BWTD 106 is on board an aircraft in response to detectinga change in air pressure over a predefined period of time (e.g., 5minutes, 15 minutes, 30 minutes, or other period of time). In otherwords, travel detection component 315 may determine that BWTD 106 is onboard an aircraft in response to determining that the air pressure isless than or equal to a threshold air pressure within a particularamount of time. In some instances, travel detection component 315determine that BWTD 106 is on board an aircraft in response todetermining that the air pressure has dropped by at least a thresholdamount within a particular amount of time.

In some examples, travel detection component 315 may determine whetherBWTD 106 is located on board an aircraft based at least in part on anon-cellular wireless network connection between BWTD 106 and a wirelesscommunication device (e.g., on board the aircraft). For example, ruledata 322 may include information associated with non-cellular wirelessnetwork expected to be available on an aircraft for a permitted flightand travel detection component 315 may compare the informationassociated with the expected wireless network to information associatedwith one or more available wireless networks. The information associatedwith the wireless network expected to be available on an aircraft flyinga permitted flight may include a device identifier (e.g., MAC address)of a networking device expected to be on board the aircraft. In someexamples, travel detection component 315 may determine that BWTD 106 islocated on board a permitted aircraft in response to determining thatthe MAC address of a networking device that broadcasts an availablewireless network matches the MAC address of the networking deviceexpected on board the permitted aircraft.

In some examples, the information associated with a non-cellularwireless network expected to be available on an aircraft flying apermitted flight includes a network identifier (e.g., SSID) of awireless network expected on board the aircraft. Travel detectioncomponent 315 may compare the network identifiers of one or moreavailable wireless networks to the network identifier of the networkexpected to be available on the aircraft. In some instances, traveldetection component 315 may determine that BWTD 106 is on board apermitted aircraft in response to determining that the SSID of anavailable network matches the SSID of a network expected to be on thepermitted aircraft. In other words, travel detection component 315 maydetermine that BWTD 106 is on board an aircraft if the SSID of anavailable WiFi® network matches the predetermined SSID of the WiFi®network expected to be available on the aircraft flying a permittedflight.

Travel detection component 315 may determine whether BWTD 106 is locatedon board the correct aircraft (e.g., an aircraft flying a permittedflight, also referred to as a permitted aircraft). In some examples,travel detection component 315 determines whether BWTD 106 is on board apermitted aircraft based on information received from the aircraft. Forexample, responsive to connecting to a wireless network, communicationcomponent 310 may request flight information (e.g., flight number,destination city, or other flight information) for the flight from acomputing device (e.g., an in-flight entertainment system) on board theaircraft. Communication component 310 may receive the flight informationfor the flight and travel detection component 315 may compare thereceived flight information to the flight information for the permittedflight. For instance, travel detection component 315 may compare theflight code (also referred to as flight number) received from theaircraft's on board computing and the current date to the flight code ofthe permitted flight and permitted travel date. Travel detectioncomponent 315 may determine that BWTD 106 is on board a permitted flightin response to determining that the flight information received from thecomputing system on board the aircraft corresponds to the flightinformation for the permitted flight. In response to determining thatBWTD 106 is on board an aircraft, notification component 314 maytemporarily refrain from outputting notifications indicating that thecurrent location (e.g., GNSS coordinates) of BWTD 106 cannot bedetermined. For example, BWTD 106 may refrain from outputting alerts(e.g., visual, audible, tactile) alerts to monitored user 104 or fromsending alerts to monitoring center 112 and/or user devices 116 utilizedby monitoring users 118.

In some examples, BWTD 106 may receive updated flight informationassociated with a permitted flight. BWTD 106 may receive the updatedflight information prior to boarding (e.g. while monitored target 104 isat the airport), after monitored target 104 boards the permittedaircraft but before takeoff, or after takeoff but before landing. Insome scenarios, the updated flight information may indicate a change inthe a aircraft assigned to fly the permitted flight (e.g., due tounscheduled maintenance on the aircraft originally assigned to fly thepermitted flight). For example, the updated flight information mayinclude a registration number of a second aircraft, networkinginformation (e.g., network identifier or networking device identifier)for a second aircraft, etc. In some instances, the updated flightinformation may indicate a change in the flight (e.g., due to weather).For instance, the updated flight information may include an updateddeparture date and/or time, departure airport, destination date and/ortime, destination airport and/or city, etc. For instance, BWTD 106 mayreceive updated flight information via the wireless non-cellular networkon board the aircraft indicating a different destination airport (e.g.,if the aircraft is re-routed to a different city due to weather near theoriginal destination).

In some examples, travel detection component 315 may command BWTD 106 tooperate in an “airplane mode” in response to determining that BWTD 106is located on board the correct, permitted aircraft (e.g., an aircraftflying a permitted flight). For example, in the airplane mode, one ormore of communication units 340 may be disabled, turned-off, or may beotherwise operating in a reduced-power state, such that the one or moredisabled communication units do not transmit or receive messages. Forinstance, travel detection component 315 may disable a cellular radiocomponent and/or GNSS components 343 in response to determining thatBWTD 106 is located on board a permitted aircraft. Disabling one or moreof communication units 340 may reduce the amount of battery powerconsumed by the one or more disabled communication units when BWTD 106is on a flight.

In some examples, travel detection component 315 causes BWTD 106A toenter the airplane mode in response to receiving a message frommonitoring center 112 indicating that non-cellular wirelesscommunication between BWTD 106 and monitoring center 112 has beenestablished. For example, an internet provider that provides internetaccess to the network on board the aircraft may request network accesscredentials before providing BWTD 106 with access to the internet, suchthat BWTD 106 may be unable to communicate with monitoring center 112via the aircraft's non-cellular wireless network until the internetprovider has granted BWTD 106 access to the internet. In some instances,BWTD 106 may receive the network access credentials from monitoringcenter 112 and/or computing device 107. Responsive to BWTD 106connecting to the network, BWTD 106 may retrieve the network accesscredentials from a volatile or non-volatile memory device (e.g., storagecomponents 338) and may send the network access credentials to thenetwork. BWTD 106 may receive a message from the internet providerindicating whether the network access credentials supplied by BWTD 106are correct. In response to receiving a message indicating that thenetwork access credentials are correct, BWTD 106 may communicate withmonitoring center 112 via the non-cellular wireless network on board theaircraft. Responsive to receiving a message from message from monitoringcenter 112 via the non-cellular wireless network, BWTD 106 may disablethe GNSS components 343 and/or cellular communication unit 352. In someinstances, BWTD 106 may disable GNSS components 343 and/or cellularcommunication unit 352 in response to receiving permission frommonitoring center 112.

Travel detection component 315 may re-enable one or more ofcommunication units 340 and/or GNSS components 343 in response todetermining that the permitted flight is complete (e.g., the aircrafthas landed). In some examples, travel detection component 315 determinesthat the flight is complete based on sensor data generated by sensorcomponents 344. For example, travel detection component may receivesensor data from accelerometer components 346 and may determine that theaircraft has landed in a similar manner as described above fordetermining when the aircraft takes off. Travel detection component 315may determine that the permitted flight is complete based on informationreceived from the aircraft's on board computing system (e.g., anin-flight entertainment system) that the aircraft has landed. Forinstance, BWTD 106 may receive messages from the on board computingsystem that indicate the position or location of the aircraft while BWTD106 is connected to the aircraft wireless network. In some instances,BWTD 106 sends messages to monitoring center 112 indicating the currentposition of the aircraft during the flight. Responsive to receiving amessage from the computing system on board the aircraft that indicatesthe aircraft has landed or the aircraft has arrived at its destination,travel detection component 315 may determine that the permitted flightis complete.

In some examples, BWTD 106 may determine that the permitted flight iscomplete in response losing a connection to the wireless network onboard the aircraft. For example, upon landing, monitored person 104 maydisembark the permitted aircraft such that BWTD 106 is no longercommunicatively coupled to the wireless network on board the aircraft.In some instances, travel detection component 315 determines that thepermitted flight is complete in response to losing a connection to thewireless network on board the aircraft for at least a threshold amountof time (e.g., one minute, five minutes, thirty minutes, etc.).

Travel detection component 315 may command BWTD 106 to cease operatingin the airplane mode and resume a normal mode of operation in responseto determining that the permitted flight is complete. For example,travel detection component 315 may re-enable one or more ofcommunication units 340 and/or GNSS components 343 in response todetermining that the permitted flight is complete. Similarly, traveldetection component may re-enable notification component 314 in responseto determining that the permitted flight is complete. As a result,notification component 314 may output notifications in response tolocation detection components 312 determining that the current GNSScoordinates of BWTD 106 cannot be determined using the GNSS components343. In some examples, notification component 314 may generate and sendnotifications (e.g., via communication components 310) to one or moreexternal computing devices such as monitoring center 112 and/orcomputing device 107 of FIG. 1. For example, the notification mayinclude a message indicating that the GNSS coordinates of BWTD 106cannot be determined and/or that BWTD 106 is no longer on board thepermitted aircraft. Additionally or alternatively, the notification mayinclude flight information (e.g., arrival city and time). In somescenarios, notification component 314 may send a command to one or moreof output components 342 to output an alert. Responsive to receiving thecommand to output an alert, one or more of output components 342 mayoutput an alert (e.g., haptic, audio, or visual feedback) that indicatesthe person wearing BWTD 106A should proceed to an area where BWTD 106can receive GNSS signals from enough satellites to determine its currentGNSS coordinates.

FIG. 4 is a block diagram illustrating example components of serverdevice 114A, in accordance with one or more aspects of the presentdisclosure. FIG. 4 illustrates only one particular example of serverdevice 114A in monitoring center 112, as shown in FIG. 1. Many otherexamples of server device 114A may be used in other instances and mayinclude a subset of the components included in example server device114A or may include additional components not shown in FIG. 4. In someexamples, server device 114A may be a server, tablet computing device,smartphone, wrist- or head-worn computing device, laptop, desktopcomputing device, or any other computing device that may run a set,subset, or superset of functionality included in application 428.

As shown in the example of FIG. 4, server device 114A may be logicallydivided into user space 402, kernel space 404, and hardware 406.Hardware 406 may include one or more hardware components that provide anoperating environment for components executing in user space 402 andkernel space 404. User space 402 and kernel space 404 may representdifferent sections or segmentations of memory, where kernel space 404provides higher privileges to processes and threads than user space 402.For instance, kernel space 404 may include operating system 420, whichoperates with higher privileges than components executing in user space402.

As shown in FIG. 4, hardware 406 includes one or more processors 408,input components 410, storage components 412, communication units 414,and output components 416. Processors 408, input components 410, storagecomponents 412, communication units 414, and output components 416 mayeach be interconnected by one or more communication channels 418.Communication channels 418 may interconnect each of the components 408,410, 412, 414, and 416 for inter-component communications (physically,communicatively, and/or operatively). In some examples, communicationchannels 418 may include a hardware bus, a network connection, one ormore inter-process communication data structures, or any othercomponents for communicating data between hardware and/or software.

One or more processors 408 may implement functionality and/or executeinstructions within server device 114A. For example, processors 408 onserver device 114A may receive and execute instructions stored bystorage components 412 that provide the functionality of componentsincluded in kernel space 404 and user space 402. These instructionsexecuted by processors 408 may cause server device 114A to store and/ormodify information, within storage components 412 during programexecution. Processors 408 may execute instructions of components inkernel space 404 and user space 402 to perform one or more operations inaccordance with techniques of this disclosure. That is, componentsincluded in user space 402 and kernel space 404 may be operable byprocessors 408 to perform various functions described herein.

One or more input components 410 of server device 114A may receiveinput. Examples of input are tactile, audio, kinetic, and optical input,to name only a few examples. Input components 410 of server device 114A,in one example, include a mouse, keyboard, voice responsive system,video camera, buttons, control pad, microphone or any other type ofdevice for detecting input from a human or machine. In some examples,input component 410 may be a presence-sensitive input component, whichmay include a presence-sensitive screen, touch-sensitive screen, etc.

One or more output components 416 of server device 114A may generateoutput. Examples of output are tactile, audio, and video output. Outputcomponents 416 of server device 114A, in some examples, include apresence-sensitive screen, sound card, video graphics adapter card,speaker, cathode ray tube (CRT) monitor, liquid crystal display (LCD),or any other type of device for generating output to a human or machine.Output components may include display components such as cathode raytube (CRT) monitor, liquid crystal display (LCD), Light-Emitting Diode(LED) or any other type of device for generating tactile, audio, and/orvisual output.

Output components 416 may be integrated with server device 114A in someexamples. In other examples, output components 416 may be physicallyexternal to and separate from server device 114A, but may be operablycoupled to server device 114A via wired or wireless communication. Anoutput component may be a built-in component of server device 114Alocated within and physically connected to the external packaging ofserver device 114A (e.g., a screen on a mobile phone). In anotherexample, an output component, such as a presence-sensitive screen, maybe an external component of server device 114A located outside andphysically separated from the packaging of server device 114A (e.g., amonitor, a projector, etc. that shares a wired and/or wireless data pathwith a tablet computer). Output components 416 may provide haptic,vibratory or other tactile output.

One or more communication units 414 of server device 114A maycommunicate with external devices by transmitting and/or receiving data.For example, server device 114A may use communication units 414 totransmit and/or receive radio signals on a radio network such as acellular radio network. Examples of communication units 414 include anetwork interface card (e.g. such as an Ethernet card), an opticaltransceiver, a radio frequency transceiver, or any other type of devicethat can send and/or receive information. Other examples ofcommunication units 414 may include Bluetooth®, 3G, 4G, and Wi-Fi®radios found in mobile devices as well as Universal Serial Bus (USB)controllers and the like.

One or more storage components 412 within server device 114A may storeinformation for processing during operation of server device 114A. Insome examples, storage device 412 is a temporary memory, meaning that aprimary purpose of storage device 412 is not long-term storage. Storagecomponents 412 on server device 114A may be configured for short-termstorage of information as volatile memory and therefore not retainstored contents if deactivated. Examples of volatile memories includerandom access memories (RAM), dynamic random access memories (DRAM),static random access memories (SRAM), and other forms of volatilememories known in the art.

Storage components 412, in some examples, also include one or morecomputer-readable storage media. Storage components 412 may beconfigured to store larger amounts of information than volatile memory.Storage components 412 may further be configured for long-term storageof information as non-volatile memory space and retain information afteractivate/off cycles. Examples of non-volatile memories include magnetichard discs, optical discs, floppy discs, flash memories, or forms ofelectrically programmable memories (EPROM) or electrically erasable andprogrammable (EEPROM) memories. Storage components 412 may store programinstructions and/or data associated with components included in userspace 402 and/or kernel space 404.

As shown in FIG. 4, application 428 executes in user space 402 of serverdevice 114A. Application 428 may be logically divided into presentationlayer 422, application layer 424, and data layer 426. Presentation layer422 may include user interface (UI) component 425, which generates andrenders user interfaces of application 428. Application layer 424 mayinclude location management component (LMC) 427, rule enforcementcomponent (REC) 429, and notification component 430.

Data layer 426 may include one or more data stores. A data store maystore data in structure or unstructured form. Example data stores may beany one or more of a relational database management system, onlineanalytical processing database, table, or any other suitable structurefor storing data. Monitored person data 434 may include informationdescriptive of monitored persons and/or monitoring users. Example data,may include unique identifier for monitored person or user, name,address, phone number, notes, or any other descriptive information of amonitored person or monitored person, such as a type of offense, adegree of offense (e.g., a legal degree of offense, such as seconddegree battery), or the like.

Location data 436 may include GNSS locations of BWTDs and other dataassociated with the GNSS locations. For instance, a record or otherinstance of location data in location data 436 may include, but is notlimited to, any one or more of: unique identifier of BWTD and/ormonitored person wearing BWTD, timestamp, GNSS coordinates (latitude,longitude), GNSS signal strength, signal strength of cellular tower, anddirectional heading of BWTD, speed at which a BWTD is traveling, whethera BWTD is at rest, an ambient temperature in which a BWTD is located,whether a BWTD is in motion without a GNSS signal, or the like. The dataincluded in a record or other instance of location data in location data436 may be a tuple or set of data sent by a BWTD to monitoring center112, as described in FIG. 1.

Data layer 426 also includes monitoring rules data 438. Monitoring rulesdata 438 may include data that define, one or more of: a restrictedarea, a permissible area, a time period for permitted travel withrespect to a restricted/permissible area, permissible/restricted userswho can or cannot be within a threshold distance of the monitoredperson, grace periods, or any other property, rule, condition, to nameonly a few examples. In some examples, monitoring rules 438 definespermitted travel (e.g., flight) information, such as permitted modes oftravel, permitted travel dates/times, permitted destinations, or otherinformation indicating when, where, or how a monitored target ispermitted to travel. For example, monitoring rules 438 may includeinformation indicating an airline and flight number of a flightmonitored target 104 is permitted to fly upon, a permitted departurecity (also referred to as a city of origin), a permitted departureairport, a permitted destination city, and/or a permitted destinationairport. In some instances, monitoring rules 438 defines a networkidentifier (e.g., SSID) or networking device identifier (e.g., MACaddress) corresponding to a wireless network expected to be available onboard a vehicle (e.g., aircraft) upon which the monitored target ispermitted to travel.

In operation, BWTD 106 may be attached and assigned to monitored target104. LMC 427 may receive a unique identifier of BWTD 106 and/or a uniqueidentifier of monitored target 104. LMC 427 may store data defining anassociation between the unique identifier of BWTD 106 and the uniqueidentifier of monitored target 104. As monitored target 104 moves withinone or more different geographic regions, LMC 427 may receive locationdata from BWTD 106 including, but not limited to: a unique identifier ofBWTD 106 and/or monitored person wearing BWTD 106, GNSS coordinates(latitude, longitude), a timestamp when the GNSS coordinates (latitude,longitude) were determined, GNSS signal strength when the GNSScoordinates (latitude, longitude) were determined, signal strength of atower when the GNSS coordinates (latitude, longitude) were determined,and/or a directional heading of BWTD 106 when the GNSS coordinates(latitude, longitude) were determined. In some scenarios, location data436 may also include a timestamp when GNSS coordinates of BWTD 106 werenot able to be determined and the last known location of BWTD 106. Inthese scenarios, location data may also include motion data generated byone or more sensor components 344 of FIG. 3, and/or a net distance andnet direction from the last known location of BWTD 106. LMC 427 maystore such location data within location data 436.

REC 429 may determine whether any other property, rule, condition ofmonitoring rules data 438 is satisfied, and which may include data thatdefines, one or more of: a restricted area, a permissible area, a timeperiod for permitted travel with respect to a restricted/permissiblearea, permissible/restricted users who can or cannot be within athreshold distance of the monitored person, or any other property, rule,condition. For instance, REC 429 may determine whether any otherproperty, rule, condition is satisfied based on receiving one or more ofGNSS locations from LMC 427, location data 436, and monitoring rulesdata 438.

Notification component 430 generate alerts. In some examples, an alertindicates that monitored target 104 is potentially at an unauthorizedlocation or that BWTD 106 is unable to determine the GNSS coordinates ofmonitored target 104. For example, notification component 430 may sendnotifications (or messages) to computing devices external to serverdevice 114A that cause such computing devices to output alerts, whichmay be visual, audio, haptic or any other type of discernable feedback.In this way, violations, statuses, or any other information may becommunicated to devices of monitored persons and monitoring users. Insome examples, events that cause notifications or messages to be sent bynotification component 430 may also be logged by LMC 427, REC 429,and/or notification component 430 in monitored person data 434.

In some examples, UI component 425 acts as an intermediary betweenvarious components and modules of server device 114A to process and sendinput detected by input devices to other components and modules, andgenerate output from other components and modules that may be presentedat one or more output devices. For instance, UI component 425 maygenerate one or more user interfaces for display, which may include dataand/or graphical representations of maps, alerts, reports, or othercommunications as described in this disclosure.

While BWTD 106 is described in FIGS. 1-3 as determining whether BWTD 106is located on board a permitted vehicle, according to some aspects ofthis disclosure, server device 114A determines whether BWTD 106 islocated on board a permitted vehicle. For example, as illustrated inFIG. 4, application layer 424 of server device 114A includes traveldetection component 432. In general, travel detection component 432 mayenable server device 114A to determine whether WTD 106 is located onboard an aircraft and if so, determine whether the aircraft is apermitted aircraft. In some instances, a permitted aircraft is anaircraft associated with a flight the monitored target 104 is permittedto travel upon. In other words, the permitted aircraft may be anaircraft assigned to fly a flight the monitored target is permitted totake.

Travel detection component 432 may determine whether BWTD 106 is locatedon board an aircraft based at least in part on a non-cellular wirelessnetwork connection between BWTD 106 and a wireless communication device(e.g., on board the aircraft). For example, server device 114A mayreceive a message from BWTD 106 via a non-cellular wireless network andmay determine whether the non-cellular wireless network corresponds to anon-cellular wireless network expected on board an aircraft flying thepermitted flight. For instance, server device 114A may receive a messagethat indicates the network identifier (e.g., SSID) of the non-cellularwireless network to which BWTD 106 is communicatively coupled, and maycompare the network identifier to the network identifier of a networkexpected to be available on the aircraft flying the permitted flight. Insome examples, travel detection component 432 may determine that BWTD106 is on board an aircraft in response to determining that the networkidentifier of the non-cellular wireless network to which BWTD 106 iscommunicatively coupled corresponds to the network identifier of thenetwork expected to be available on the permitted flight.

Travel detection component 432 may determine whether BWTD 106 is onboard the correct aircraft (e.g., an aircraft flying a permitted flight,also referred to as the permitted aircraft) based on the deviceidentifier of the wireless networking device to which BWTD 106 iscommunicatively coupled. For instance, sever device 114A may receive anindication of the MAC address of the networking device to which the BWTD106 is coupled and may compare the received MAC address to the MACaddress for a networking device on board the permitted flight. In someexamples, travel detection component 432 determine that BWTD 106 is onboard a permitted aircraft in response to determining that thenetworking device identifier of the non-cellular networking device towhich BWTD 106 is communicatively coupled corresponds to the deviceidentifier of a networking device expected to be available on thepermitted flight.

In some examples, travel detection component 432 may determine whetherBWTD 106 is located on board the correct, permitted aircraft based oninformation received from the aircraft. For example, responsive to BWTD106 connecting to a non-cellular wireless network of an aircraft, serverdevice 114A may receive a message that includes flight information(e.g., flight number, destination city, or other flight information) forthe aircraft. For instance, BWTD 106 may query a computer on board theaircraft (e.g., an in-flight entertainment system) of the aircraft forthe flight information and may send the flight information to serverdevice 114A. Server device 114A may receive the flight information forthe aircraft and may compare the received flight information to theflight information for the permitted flight. In some examples, traveldetection component 432 may determine whether BWTD 106 is on board apermitted flight in based on a comparison of the received flightinformation and the flight information for the permitted flight. Forinstance, travel detection component 432 may compare the flight code andthe current date to the flight code of the permitted flight andpermitted travel date. Travel detection component 432 may determine thatBWTD 106 is on board a permitted flight in response to determining thatthe flight information received from the on board computer correspondsto the flight information for the permitted flight.

Travel detection component 432 may send a message to BWTD 106 enablingor permitting BWTD 106 to operate in an “airplane mode” in response todetermining that BWTD 106 is located on board a permitted flight. Forexample, travel detection component 432 may send a message to BWTD 106via a communication unit 414 instructing BWTD 106 to place cellularcommunication units 352 and/or GNSS components 343 into a low powerstate (e.g., turned off, or using relatively less power than duringnormal operation), which may reduce the amount of power consumed by BWTD106 during the permitted flight.

Travel detection component 432 may track BWTD 106 and/or the permittedaircraft during the permitted flight. For example, during a permittedflight, server device 114 may receive messages from BWTD 106 and/or thepermitted aircraft. The messages may indicate the flight status (e.g.,waiting to depart, in-flight, arrived, etc.), location of the permittedaircraft, etc. In some examples, notification component 430 may refrainfrom outputting notifications or alerts while BWTD 106 is on board apermitted flight. For example, while BWTD 106 may not receive GNSSsignals from a sufficient number of GNSS satellites to determine itsGNSS coordinates during the flight, notification component 430 of serverdevice 114A may refrain from outputting an alert indicating BWTD 106indicating the GNSS coordinates are unavailable in response todetermining that BWTD 106 is located on board a permitted flight. Forinstance, notification component 430 may refrain from sending alerts touser devices 116 utilized by monitoring users 118 that indicate thecurrent location of BTWD 106 is unavailable.

In some examples, travel detection component 432 determines whether thepermitted flight is complete (e.g., has landed, is at the gate, etc.).Travel detection component 432 may determine that the permitted aircraftis complete based on received flight information. For example, thereceived flight information may indicate the current location of theaircraft and travel detection component 432 may determine that thecurrent location of the aircraft corresponds to the destination of theaircraft. In some scenarios, server device 114A may receive anotification that the destination for the approved flight has changed(e.g., due to inclement weather at the original destination). In suchscenarios, travel detection component 432 may determine that the flightis complete in response to determining that the location of the aircraftcorresponds to the updated destination airport or city. Additionally oralternative, the received flight information may indicate the aircrafthas landed and/or is at the gate.

In some examples, server device 114A may cease receiving informationfrom BWTD 106 over a non-cellular communication network and maydetermine that the permitted flight is complete. For example, uponlanding, monitored person 104 may disembark the permitted aircraft suchthat BWTD 106 is no longer communicatively coupled to the non-cellularwireless network on board the aircraft. In some instances, traveldetection component 432 determines the amount of elapsed time sincereceiving a message from BWTD 106 over a non-cellular communicationnetwork. In response to determining that the elapsed time sincereceiving a message from BWTD 106 over a non-cellular communicationnetwork is at least a threshold amount of time, server device 114A maydetermine that the permitted flight is complete.

Responsive to determining the permitted flight is complete, serverdevice 114A may resume normal monitoring of BWTD 106. For example,during normal monitoring of BWTD 106, notification component 430 ofserver device 114A may output notifications or alerts in response todetermining that the GNSS coordinates of BWTD 106 are unavailable.

In some examples, travel detection component 432 may send a message toBWTD 106 commanding BWTD 106 to re-enable one or more communicationunits 343 of BWTD 106. For example, travel detection component 432 maycommand BWTD 106 to exit the airplane mode and re-enable the cellularcommunication units 352 and/or GNSS components 343 in response todetermining that the permitted flight is complete.

FIGS. 5A-5B include a flow diagram illustrating example operations ofmonitoring system 100, in accordance with one or more aspects of thisdisclosure. While described with respect to monitoring system 100 ofFIG. 1, it should be understood that the process described with respectto FIG. 6 may be carried out by a variety of other systems.

In the example of FIG. 5A, monitoring center 112 receives a message frommonitored target 104 requesting permission to travel (502). For example,monitored target 104 may submit a request to travel on a particularflight on particular date (e.g., computing device 107, etc.). Monitoringcenter 112 may store an indication of the request.

Monitoring center 112 may determine whether the travel request isgranted (504). In some examples, monitoring center 112 may automaticallydetermine whether to grant the travel request based on previous travel,terms of parole for the monitored person 104, etc. In some examples,monitoring center 112 may send the request to a user device 116 utilizedby monitoring user 118 and monitoring user 118 may approve or deny thetravel request. Responsive to determining that the travel request wasnot granted (“NO” branch of 504), monitoring center 112 and/or BWTD 106may track monitored target 104 according to normal monitoring rules inmonitoring rules 438 and rules data 322, respectively (506).

Responsive to determining that the travel request is granted, (“YES”branch of 504), monitoring system 112 and/or BWTD 106 may update therules data for monitored target 104 (508). For example, monitoringcenter 112 may update monitoring rules 438 stored at server device 114Ato include flight information for the travel request, such as apermitted travel date, permitted place of departure, permitteddestination, flight code or flight number of a permitted flight, etc.The flight information may include wireless networking informationassociated with a non-cellular wireless network expected on board apermitted aircraft, a non-cellular wireless network expected to beavailable at a permitted airport (e.g., departure airport and/ordestination airport), or both. For instance, the flight information mayinclude a network identifier (e.g., SSID) or networking deviceidentifier (e.g., MAC address) corresponding to a wireless network atthe airport, on board the aircraft, or both.

In some instances, monitoring center 112 sends the flight informationassociated with the travel request to BWTD 106. In such instances, BWTD106 may update rules data 322 to include the flight information.

In some examples, monitoring center 112 and/or BWTD 106 determineswhether monitored target 104 is at an airport (510). BWTD 106 ormonitoring center 112 may determine whether BWTD 106, and hencemonitored person 104, is at an airport based on the GNSS coordinates ofBWTD 106. For example, monitoring center 112 may determine whether theGNSS coordinates of BWTD 106 correspond to a permitted departureairport. In some instances, BWTD 106 may activate a non-cellularcommunication unit 354 (e.g., WiFi® component) in response todetermining that BWTD 106 is located at an airport or is within athreshold distance (e.g., 1 mile, one-half mile, etc.) of the permitteddeparture airport. In some instances, the non-cellular communicationunit 354 may be scheduled to turn on at certain times (e.g., a thresholdamount of time prior to a scheduled flight) or may be always on.

In some examples, responsive to determining that monitored target 104 isat the departure airport (“YES” branch of 510), monitoring center 112and/or BWTD 106 may determine whether an available non-cellular wirelessnetwork (e.g., WiFi® network) corresponds to a non-cellular wirelessnetwork expected to be available at the airport (512). For example, BWTD106 and/or monitoring center 112 may determine whether an availablenon-cellular wireless network matches a predetermined wireless networkexpected to be available at the airport. For instance, BWTD 106 maycompare a network identifier (e.g., SSID) or networking deviceidentifier (e.g., MAC address) corresponding to one or more availablenetworks to a network identifier or networking device identifiercorresponding to a non-cellular wireless network expected to beavailable at the departure airport.

Responsive to determining that there are not any available non-cellularwireless networks that correspond to a non-cellular wireless networkexpected to be available at the airport (“NO” branch of 512), monitoringcenter 112 and/or BWTD 106 may track monitored target 104 according tonormal monitoring rules in monitoring rules 438 and rules data 322,respectively (506).

In some examples, BWTD 106 connects to the expected non-cellularwireless network at the departure airport (516) in response todetermining that an available non-cellular wireless network correspondsto a non-cellular wireless network expected to be available at theairport (“YES” branch of 512). BWTD 106 may deactivate GNSS componentsin response to determining that an available non-cellular wirelessnetwork corresponds to a non-cellular wireless network expected to beavailable at the departure airport (“YES” branch of 512). In someinstances, BWTD 106 may automatically place the GNSS components 343 intoan “airplane mode” in response to connecting to the expectednon-cellular wireless network. In some instances, BWTD 106 may send amessage to monitoring center 112 indicating that BWTD 106 has connectedto the expected non-cellular wireless network (also referred to aspredetermined non-cellular wireless network) at the airport and mayreceive a message from monitoring center 112 indicating that BWTD 106may temporarily place the GNSS components 343 of BWTD 106 into theairplane mode (e.g., turn-off or enter a low-power mode). In someexamples, BWTD 106 and/or monitoring center 112 may refrain fromoutputting notifications that the GNSS coordinates are unavailable whileBWTD 106 is connected to the non-cellular wireless network expected tobe available at the departure airport.

Monitoring center 112 and/or BWTD 106 may determine whether an availablenon-cellular wireless network corresponds to a non-cellular wirelessnetwork expected to be available on board the permitted aircraft (518).For example, BWTD 106 and/or monitoring center 112 may determine whetheran available non-cellular wireless network matches a predeterminedwireless network expected to be available on board the permittedaircraft. For instance, BWTD 106 may compare a network identifier (e.g.,SSID) or networking device identifier (e.g., MAC address) correspondingto one or more available networks to a network identifier or networkingdevice identifier corresponding to a non-cellular wireless networkexpected to be available at the departure airport. BWTD 106 maydetermine that the predetermined non-cellular wireless network expectedto be available at the departure airport is available when thenetworking information (e.g., network identifier and/or networkingdevice identifier) of the expected non-cellular wireless network matchesthe networking information of an available non-cellular wirelessnetwork. In some scenarios, BTWD 106 may determine that BWTD 106 is onboard an aircraft based on determining whether an available non-cellularwireless network corresponds to a non-cellular wireless network expectedto be available on board the permitted aircraft. In other words, when anavailable non-cellular wireless network corresponds to the non-cellularwireless network expected to be available on board the permittedaircraft, this may indicate that BWTD 106 is located on board thepermitted aircraft. Thus, in some examples, BWTD 106 may determine thatBWTD 106 is on board an aircraft in response to determining that anavailable non-cellular wireless network corresponds to a non-cellularwireless network expected to be available on board the permittedaircraft.

Responsive to determining that there are not any available non-cellularwireless networks that correspond to a non-cellular wireless networkexpected to be available on the permitted aircraft (“NO” branch of 518),BWTD 106 remains connected to the expected airport non-cellular wirelessnetwork (516). Responsive to determining that an available non-cellularwireless network corresponds to a non-cellular wireless network expectedto be available on board the permitted aircraft (“YES” branch of 518),BWTD 106 may connect to the expected non-cellular wireless network onboard the aircraft (520).

BWTD 106 and/or monitoring center 112 may determine whether monitoredtarget 104 is on board the correct, permitted aircraft (522). Forexample, responsive to connecting to a wireless network on board anaircraft, BWTD 106 may request flight information (e.g., flight number,destination city, or other flight information) from the aircraft (e.g.,from an in-flight entertainment system of the aircraft). In someexamples, BWTD 106 receives the actual flight information for theaircraft and compares the actual flight information received from theaircraft to the flight information for the permitted flight. In someinstances, BWTD 106 sends the actual flight information for the aircraftto which BWTD 106 is communicatively coupled to monitoring center 112(e.g., via the non-cellular wireless network on board the aircraftand/or a cellular network). Monitoring center 112 may receive the actualflight information for the aircraft to which BWTD 106 is communicativelycoupled and may determine whether BWTD 106, and hence monitored target104, is on board the correct, permitted aircraft by comparing the actualflight information to the expected flight information for the permittedflight. For instance, BWTD 106 and/or monitoring center 112 may comparethe actual flight code received from the aircraft computing system andthe current date to the flight code of the permitted flight andpermitted travel date. Thus, BWTD 106 and/or monitoring center 112 maydetermine that BWTD 106 is on board a permitted flight if the flightinformation received from the on board computing system corresponds tothe flight information for the permitted flight.

Responsive to determining that monitored target 104 is not on board thecorrect, permitted aircraft (“NO” branch of 522), monitoring center 112and/or BWTD 106 may alert monitoring user 118 (e.g., law enforcementpersonnel) that monitored target 104 is on board an aircraft that themonitored target 104 is not permitted to be on (524). For example,monitoring center 112 may send a notification to a user device 116utilized by a monitoring user 118 (e.g., parole officer, airportsecurity personnel, airline personnel, etc.) indicating that monitoredperson 114 is on board a flight he or she is not permitted to be on.Thus, in some scenarios, the aircraft on which monitored person 104 islocated may remain grounded until monitored person 104 is no longer onboard an aircraft which he or she is not permitted to be on.

Responsive to determining that monitored target 104 is on board thecorrect, permitted aircraft (“YES” branch of 522), BWTD 106 may enter an“airplane mode” (526). In the airplane mode, BWTD 106 may temporarilydisable or deactivate GNSS components 343 of BWTD 106. Additionally oralternatively, BWTD 106 may disable or deactivate one or more cellularcommunication units of BWTD 106. In other words, BWTD 106 may turn-offGNSS components 343 and/or one or more cellular components of BWTD 106,or otherwise place such components into a low power state, which mayincrease the battery life of BWTD 106. In some examples, BWTD 106 and/ormonitoring center 112 may temporarily refrain from generating alertsindicating that the current GNSS coordinates of BTWD 106 cannot bedetermined in response to determining that BWTD 106 is located on boardan aircraft or in response determining that BWTD 106 is located on boarda permitted aircraft.

BWTD 106 and/or monitoring center 112 may determine whether BWTD 106 hasbeen tampered with during a flight (528). For example, monitoring center112 may determine whether the non-cellular wireless communicationbetween BWTD 106 and the permitted aircraft was lost for at least athreshold amount of time. For instance, a loss of communication betweenBWTD 106 and the non-cellular wireless network on board the permittedaircraft may indicate monitored user 104 attempted to shield BWTD 106from communicating with the non-cellular wireless network on board theaircraft. Similarly, BWTD 106 may detect attempts to physically removeBWTD 106 from monitored target 104. Responsive to determining that BWTD106 has been tampered with, monitoring center 112 and/or BWTD 106 mayalert law enforcement (524). For example, monitoring center 112 may senda message to monitoring user 118 (e.g., law enforcement personnel) atthe destination that indicates the identity of monitored target 104 andthe flight details for monitored target 104.

BWTD 106 and/or monitoring center 112 may determine whether thepermitted flight is complete (532). In some examples, BWTD 106determines whether the flight is complete based on sensor data generatedby sensor components 344. For example, BWTD 106 may receive accelerationdata from accelerometer components 346 and may compare the accelerationdata to a template acceleration pattern corresponding to an aircraftlanding. For instance, BWTD 106 may determine that the aircraft haslanded and hence the flight is complete in response to determining thatat least a portion of the acceleration data generated by anaccelerometer of BWTD 106 corresponds to the template accelerationpattern for an aircraft landing. In some examples, BWTD 106 and/ormonitoring center 112 determines that the permitted flight is completebased on information received from the onboard computing system. Forinstance, BWTD 106 may receive messages from the aircraft's onboardcomputing system that indicate the position or location of the aircraftwhile BWTD 106 is connected to the aircraft wireless network. In someinstances, BWTD 106 sends messages to monitoring center 112 indicatingthe current position of the aircraft during the flight. Responsive toreceiving a message from the computing system on board the aircraft thatindicates the aircraft has landed or the aircraft has arrived at itsdestination, BWTD 106 and/or monitoring center 112 may determine thatthe permitted flight is complete. BWTD 106 and/or monitoring center 112may continue to monitor for tampering of BWTD 106 (528) and/orcompletion of the flight (532) in response to determining that theflight is not complete (“NO” branch of 532).

Responsive to determining that the flight is complete (“YES” branch of532), BWTD 106 may re-enable the cellular communication units 352 (534).For example, monitoring center 112 may send a message to BWTD 106commanding BWTD 106 to re-enable the cellular communication units 352 inresponse to determining that the flight is complete. In some instances,BWTD 106 may automatically re-enable the cellular communication units352 in response to determining that the flight is complete.

BWTD 106 and/or monitoring center 112 may determine whether BWTD 106 isconnected to a cellular network in response to re-enabling the cellularcommunication units 352. For instance, BWTD 106 may determine whetherBWTD 106 is connected to a cellular network by searching for radiosignals from one or more cellular towers. In some examples, monitoringcenter 112 may determine whether BWTD 106 is connected to a cellularnetwork by attempting to communicate with BWTD 106 via a cellularnetwork. In some instances, monitoring center 112 may send a message toBWTD 106 (e.g., via cellular or non-cellular communication units)commanding BWTD 106 to send a message to monitoring center 112 via thenon-cellular communication units and may determine that the cellularcommunication is not connected to the cellular network if BWTD 106 doesnot send a response via a cellular network.

Responsive to determining that BWTD 106 is not connected to a cellularnetwork (“NO” branch of 536), monitoring center 112 and/or BWTD 106 mayalert law enforcement (524). For example, monitoring center 112 may senda notification to law enforcement personnel indicating that monitoredperson 104 is on a particular flight and that cellular communicationwith BWTD 106 is not working. In some instances, law enforcementpersonnel may meet monitored target 104 at the airport gate (e.g., tocheck if BWTD 106 is working properly).

Responsive to determining that BWTD 106 is connected to a cellularnetwork (“YES” branch of 536), BWTD 106 and/or monitoring center 112 maydetermine whether monitored target 104 is still located on the aircraft(540). In some examples, BWTD 106 may determine whether monitored target104 is still located on the aircraft based on sensor data generated byone or more sensor components 344 of BWTD 106. For example, BWTD 106 maydetermine that monitored target 104 is still on board the aircraft inresponse to determining that a number of steps detected by BWTD 106since the aircraft landed is less than or equal to a threshold number ofsteps. For instance, the number of steps taken since landing mayindicate whether the monitored target 104 has walked far enough to gofrom the back of the plane to the front of the plane. In some instances,BWTD 106 determines that monitored target 104 is still on board theaircraft based on the net distance (e.g., straight line distance) from astarting location to a current location. For instance, monitored target104 may take numerous steps while on the plane but the net distance maybe small (e.g., walking from his or her seat to a bathroom and then backto the seat). Thus, in some scenarios, BWTD 106 may determine that BWTDis still located on board the aircraft if the net distance traveled isless than or equal to a threshold distance. In some examples, BWTD 106and/or monitoring center 112 may determine whether monitored target 104is still located on board the aircraft based on whether BWTD 106 isstill connected to the non-cellular wireless network on board thepermitted aircraft.

If BWTD 106 and/or monitoring center 112 determines that BWTD 106 isstill on board the aircraft, BWTD 106 and/or monitoring center 112 maycontinue to monitor BWTD 106 to determine whether and when monitoredtarget 104 disembarks the aircraft (540). In response to determiningthat BWTD 106 is no longer on the aircraft, BWTD 106 may re-enable GNSScomponents 343 of BWTD 106. For example, BWTD 106 may automaticallyre-enable GNSS components 343 is response to BWTD 106 determining thatBWTD 106, and thus monitored target 104, is no longer on the aircraft.In some scenarios, monitoring center 112 may determine that BWTD 106 isnot on the aircraft and may send a message to BWTD 106 (e.g., viacellular communication units) commanding BWTD 106 to re-enable GNSScomponents 343 of BWTD 106.

BWTD 106 may determine whether the GNSS coordinates of BWTD 106 aredeterminable (542). For example, BWTD 106 may determine whether BWTD 106receives signals from a sufficient number (e.g., three or more) of GNSSsatellites to determine GNSS coordinates of BWTD 106. For instance,monitored target 104 may be located inside the airport at thedestination of the permitted flight and the structure of the airport mayblock communications between BWTD 106 and one or more GNSS satellites.Responsive to determining that the GNSS coordinates of BWTD 106 aredeterminable (“YES” branch of 542), BWTD 106 may determine its currentGNSS coordinates and resume normal monitoring of monitored target 104(548). In some instances, BWTD 106 may disable or deactivate thenon-cellular wireless communication units 354 in response to determiningthe GNSS coordinates of BWTD 106.

In response to determining that the GNSS coordinates for BWTD 106 cannotbe determined (“NO” branch of 542), monitoring center 112 and/or BWTD106 may determine whether a non-cellular wireless network expected to beavailable at the destination airport is actually available (544).Monitoring center 112 and/or BWTD 106 may determine whether an availablenon-cellular wireless network corresponds to a non-cellular wirelessnetwork expected to be available at the airport (518). For example, BWTD106 and/or monitoring center 112 may determine whether an availablenon-cellular wireless network matches a predetermined wireless networkexpected to be available at the destination airport. For instance, BWTD106 may compare a network identifier (e.g., SSID) or networking deviceidentifier (e.g., MAC address) corresponding to one or more availablenetworks to a network identifier or networking device identifiercorresponding to a non-cellular wireless network expected to beavailable at the destination airport. BWTD 106 may determine that thepredetermined non-cellular wireless network expected to be available atthe departure airport is available when the networking information(e.g., network identifier and/or networking device identifier) of theexpected non-cellular wireless network matches the networkinginformation of an available non-cellular wireless network.

In some examples, BWTD 106 may resume normal monitoring operations (548)in response to determining that the non-cellular wireless networkexpected to be available at the destination airport is not available(“NO” branch of 542).

Responsive to determining that the expected non-cellular wirelessnetwork is available (“YES” branch of 542), BWTD 106 may connect to theexpected non-cellular wireless network (546). In other words, if thepredetermined network (e.g., WiFi® network) for the destination airportis available, BWTD 106 may connect to the predetermined network at thedestination airport. BWTD 106 may send a message to monitoring center112 indicating that BWTD 106 is still within the destination airport. Insome examples, BWTD 106 and/or monitoring center 112 may refrain fromoutputting notifications that the GNSS coordinates are unavailable whileBWTD 106 is connected to the predetermined non-cellular wireless networkat the destination airport.

In one or more examples, the functions described may be implemented inhardware, software, firmware, or any combination thereof. If implementedin software, the functions may be stored on or transmitted over, as oneor more instructions or code, a computer-readable medium and executed bya hardware-based processing unit. Computer-readable media may includecomputer-readable storage media, which corresponds to a tangible mediumsuch as data storage media, or communication media including any mediumthat facilitates transfer of a computer program from one place toanother, e.g., according to a communication protocol. In this manner,computer-readable media generally may correspond to (1) tangiblecomputer-readable storage media, which is non-transitory or (2) acommunication medium such as a signal or carrier wave. Data storagemedia may be any available media that can be accessed by one or morecomputers or one or more processors to retrieve instructions, codeand/or data structures for implementation of the techniques described inthis disclosure. A computer program product may include acomputer-readable medium.

By way of example, and not limitation, such computer-readable storagemedia can comprise RAM, ROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage, or other magnetic storage devices, flashmemory, or any other medium that can be used to store desired programcode in the form of instructions or data structures and that can beaccessed by a computer. Also, any connection is properly termed acomputer-readable medium. For example, if instructions are transmittedfrom a website, server, or other remote source using a coaxial cable,fiber optic cable, twisted pair, digital subscriber line (DSL), orwireless technologies such as infrared, radio, and microwave, then thecoaxial cable, fiber optic cable, twisted pair, DSL, or wirelesstechnologies such as infrared, radio, and microwave are included in thedefinition of medium. It should be understood, however, thatcomputer-readable storage media and data storage media do not includeconnections, carrier waves, signals, or other transient media, but areinstead directed to non-transient, tangible storage media. Disk anddisc, as used, includes compact disc (CD), laser disc, optical disc,digital versatile disc (DVD), floppy disk and Blu-ray disc, where disksusually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above should also be includedwithin the scope of computer-readable media.

Instructions may be executed by one or more processors, such as one ormore digital signal processors (DSPs), general purpose microprocessors,application specific integrated circuits (ASICs), field programmablelogic arrays (FPGAs), or other equivalent integrated or discrete logiccircuitry. Accordingly, the term “processor”, as used may refer to anyof the foregoing structure or any other structure suitable forimplementation of the techniques described. In addition, in someaspects, the functionality described may be provided within dedicatedhardware and/or software modules. Also, the techniques could be fullyimplemented in one or more circuits or logic elements.

The techniques of this disclosure may be implemented in a wide varietyof devices or apparatuses, including a wireless handset, an integratedcircuit (IC) or a set of ICs (e.g., a chip set). Various components,modules, or units are described in this disclosure to emphasizefunctional aspects of devices configured to perform the disclosedtechniques, but do not necessarily require realization by differenthardware units. Rather, as described above, various units may becombined in a hardware unit or provided by a collection ofinteroperative hardware units, including one or more processors asdescribed above, in conjunction with suitable software and/or firmware.

It is to be recognized that depending on the example, certain acts orevents of any of the methods described herein can be performed in adifferent sequence, may be added, merged, or left out altogether (e.g.,not all described acts or events are necessary for the practice of themethod). Moreover, in certain examples, acts or events may be performedconcurrently, e.g., through multi-threaded processing, interruptprocessing, or multiple processors, rather than sequentially.

In some examples, a computer-readable storage medium includes anon-transitory medium. The term “non-transitory” indicates, in someexamples, that the storage medium is not embodied in a carrier wave or apropagated signal. In certain examples, a non-transitory storage mediumstores data that can, over time, change (e.g., in RAM or cache).

Various examples have been described. These and other examples arewithin the scope of the following claims.

The invention claimed is:
 1. A method comprising: determining, by abody-worn tracking device (BWTD), whether the BWTD is located on boardan aircraft; and responsive to determining that the BWTD is located onboard the aircraft: disabling, by the BWTD, a GNSS device of the BWTDand a cellular communication unit of the BWTD; temporarily refraining,by the BWTD, from generating an alert that indicates a current locationof the BWTD cannot be determined, wherein determining whether the BWTDis located on board the aircraft comprises: receiving, by the BWTD, adevice identifier corresponding to a wireless communication device thatis communicatively coupled to a non-cellular communication unit of theBWTD; determining, by the BWTD, based on the device identifiercorresponding to the wireless communication device, whether the wirelesscommunication device is associated with the aircraft; determining, bythe BWTD, that the BWTD is located on the aircraft based on determiningthat the wireless communication device is associated with the aircraft,sending, by the BWTD and to the wireless communication device associatedwith the aircraft, network access credentials associated with a wirelessnetwork expected to be available on the aircraft; receiving, by the BWTDand from the wireless communication device associated with the aircraftand via the non-cellular communication unit, an indication that thenetwork access credentials are correct, sending, by the BWTD, to aremote computing device and via the non-cellular communication unit, amessage indicating the BWTD is communicatively coupled to the wirelesscommunication device associated with the aircraft; and receiving, by theBWTD and from the remote computing device, a message permitting the BWTDto disable the GNSS device, wherein disabling the GNSS device isresponsive to receiving an indication that the network accesscredentials are correct, or to receiving the message permitting the BWTDto disable the GNSS device.
 2. The method of claim 1, furthercomprising: further responsive to determining that the BWTD is locatedon the aircraft, determining, by the BWTD, whether the aircraft is apermitted aircraft on which an individual assigned to wear the BWTD ispermitted to travel, wherein temporarily refraining from generating thealert is further responsive to determining that the aircraft is thepermitted aircraft, further wherein determining whether the aircraft isa permitted aircraft on which an individual assigned to wear the BWTD ispermitted to travel comprises: determining, by the BWTD, flightinformation for the aircraft; determining, by the BWTD, whether theflight information for the aircraft corresponds to expected flightinformation for the permitted aircraft; and determining, by the BWTD,that the aircraft is the permitted aircraft in response to determiningthat the flight information for the aircraft corresponds to expectedflight information for the permitted aircraft.
 3. The method of claim 2,wherein the flight information for the aircraft includes at least oneof: a flight number of the aircraft, a departure date of the aircraft,airline associated with the aircraft, a departure location of theaircraft, or a destination location of the aircraft.
 4. The method ofclaim 3, further comprising: responsive to determining that the aircraftis not the permitted aircraft, outputting, by the BWTD, a messageindicating the individual assigned to wear the BWTD is located on anaircraft that is not the permitted aircraft.
 5. The method of claim 1,wherein determining whether the BWTD is located on the aircraftcomprises determining whether the BWTD is located on the aircraft at afirst time, the method further comprising: determining, by the BWTD andat a second time that is later than the first time, whether the aircrafthas landed; and responsive to determining that the aircraft has landed:enabling, by the BWTD, the GNSS device and the cellular communicationunit; determining, by the BWTD, whether GNSS coordinates of the BWTD atthe second dine are known; and responsive to determining that the GNSScoordinates of the BWTD at the second time are known, sending, by theBWTD and to a remote computing device via the cellular communicationunit, an indication of the GNSS coordinates of the BWTD at the secondtime.
 6. The method of claim 5, further comprising: responsive todetermining that the GNSS coordinates of the BWTD at the second time arenot known, determining, by the BWTD, whether a predetermined WiFinetwork is available; and responsive to determining that thepredetermined WiFi network is available: connecting, by the BWTD, to theWiFi network; and sending, by the BWTD and to the remote computingdevice, a message indicating that the BWTD is communicatively connectedto the predetermined WiFi network.
 7. The method of claim 1, whereindetermining whether the BWTD is located on the aircraft comprisesdetermining whether the BWTD is located on the aircraft at a first time,the method further comprising: determining, by the BWTD and at a secondtime that is earlier than the first time, whether the BWTD is locatedwithin a predetermined distance of an airport; and responsive todetermining that the BWTD is within the predetermined distance of theairport, enabling a non-cellular wireless communication unit of theBWTD.
 8. The method of claim 1, wherein determining whether the BWTD islocated on an aircraft comprises: receiving, by the BWTD and from atleast one motion sensor of the BWTD, an indication of acceleration; anddetermining, by the BWTD, based on the indication of e acceleration andan acceleration profile, whether the BWTD is located on the aircraft. 9.A method comprising: determining, by one or more processors, whether abody-worn tracking device (BWTD) is located on board an aircraft; andresponsive to determining that the BWTD is located on board theaircraft, temporarily refraining, by the one or more processors, fromgenerating an alert that indicates a current location of the BWTD cannotbe determined wherein determining whether the BWTD is located on board,the aircraft comprises: receiving, by the BWTD, a device identifiercorresponding to a wireless communication device that is communicativelycoupled to a non-cellular communication unit of the BWTD; determining,by the BWTD, based on the device identifier corresponding to thewireless communication device, whether the wireless communication deviceis associated with the aircraft; determining, by the BWTD, that the BWTDis located on the aircraft based on determining that the wirelesscommunication device is associated with the aircraft, sending, by theBWTD and to the wireless communication device associated with theaircraft, network access credentials associated with a wireless networkexpected to be available on the aircraft; receiving, by the BWTD andfrom the wireless communication device associated with the aircraft andvia the non-cellular communication unit, an indication that the networkaccess credentials are correct, sending, by the BWTD, to a remotecomputing device and via the non-cellular communication unit, a messageindicating the BWTD is communicatively coupled to the wirelesscommunication device associated with the aircraft; and receiving, by theBWTD and from the remote computing device, a message permitting the BWTDto disable the GNSS device, wherein disabling the GNSS device isresponsive to receiving an indication that the network accesscredentials are correct, or to receiving the message permitting the BWTDto disable the GNSS device.
 10. The method of claim 9, furthercomprising: receiving a travel request associated with the BWTD;receiving expected flight information associated with the travelrequest; determining whether the travel request has been approved; andresponsive to determining that the travel request has been approved,updating monitoring rules associated with the BWTD to include theexpected flight information.
 11. The method of claim 10, wherein theexpected flight information comprises a flight number, the methodfurther comprising: receiving, from a travel provider, based at least inpart on the flight member, information indicative of a wireless networkon board a permitted flight.
 12. The method of claim 9, furthercomprising: responsive to determining that the BWTD is located on boardthe aircraft: sending, by the one or more processors and to the BWTD, amessage enabling the BWTD to disable at least one of a GNSS device ofthe BWTD or a cellular communication unit of the BWTD.
 13. The method ofclaim 9, further comprising: further responsive to determining that theBWTD is located on the aircraft, determining, by the one or moreprocessors, whether the aircraft is a permitted aircraft on which anindividual assigned to wear the BWTD is permitted to travel, whereintemporarily refraining from generating the alert is further responsiveto determining that the aircraft is the permitted aircraft.
 14. Themethod of claim 13, wherein determining whether the aircraft is apermitted aircraft on which an individual assigned to wear the BWTD ispermitted to travel comprises: receiving, by the one or more processors,flight information for the aircraft; determining, by the one or moreprocessors, whether the flight information for the aircraft correspondsto expected flight information for the permitted aircraft; anddetermining, by the one or more processors, that the aircraft is thepermitted aircraft in response to determining that the flightinformation for the aircraft corresponds to expected flight informationfor the permitted aircraft, wherein the flight information for theaircraft includes at least one of: a flight number of the aircraft, adeparture date of the aircraft, airline associated with the aircraft, adeparture location of the aircraft, or a destination location of theaircraft.
 15. The method of claim 14, further comprising: responsive todetermining that the aircraft is not the permitted aircraft, outputting,by the one or more processors, a message indicating the individualassigned to wear the BWTD is located on an aircraft that is not thepermitted aircraft.
 16. The method of claim 9, wherein determiningwhether the BWTD is located on the aircraft comprises determiningwhether the BWTD is located on the aircraft at a first time, the methodfurther comprising: determining, by the one or more processors and at asecond time that is later than the first time, whether the aircraft haslanded; and responsive to determining that the aircraft has landed:sending, by the one or more processors and to the BWTD, a command toenable the GNSS device and the cellular communication unit.
 17. Themethod of claim 9, wherein determining whether the BWTD is located onthe aircraft comprises determining whether the BWTD is located on theaircraft at a first time, the method further comprising: determining, bythe one or more processors and at a second time that is earlier than thefirst time, whether the BWTD is located within a predetermined distanceof an airport; and responsive to determining that the BWTD is within thepredetermined distance of the airport, sending, by the one or moreprocessors and to the BWTD, a message instructing the BWTD to enable anon-cellular wireless communication unit of the BWTD.